openapi: 3.0.1 info: title: Hubflo chat_room webhook API version: v2 description: "The Hubflo API allows you to write and read data from the Hubflo application.\nIt conforms to [REST](https://en.wikipedia.org/wiki/REST).\nIt has predictable resource-oriented URLS, accepts JSON request bodies, returns JSON and uses standard HTTP status codes\nand verbs.\n\n# Authentication\n\nThe Hubflo API requires authentication.\nIt's a bearer authentication, also called token authentication.\n\nTo start your integration journey with the Hubflo API, you must send your **authentication token** in the\n`Authorization` header when making requests to the API.\n\n```\nAuthorization: Bearer \n```\n\n# Getting started\n\nNavigate to [https://app.hubflo.com/organizations/](https://app.hubflo.com/organizations/).\nIn the **Integrations** settings panel, click on the **Generate key** button if you don't already have an API key.\n\nThe generated API key is the required authentication token you must send in the `Authorization` header.\nLet's copy it.\n\nYou can use the `/pings` endpoint to check that you can successfully make an authenticated request.\nDo it directly from this documentation, using the **Authorize** button to paste your authentication token, then push\nthe **Try it out** button.\n\nAlternatively, you can run the following cURL command in a terminal:\n\n```\ncurl -X 'POST' \\\n 'https://app.hubflo.com/api/v2/pings' \\\n -H 'accept: application/json' \\\n -H 'Authorization: Bearer ' \\\n -d ''\n```\n\nIf you're successfully authenticated, you receive:\n\n```json\n{\n \"pong\": \"ok\"\n}\n```\n\nOtherwise you get a `401 - Unauthorized` error. For example:\n\n```json\n{\n \"status\": 401,\n \"title\": \"Unauthorized\",\n \"message\": \"API token not found\"\n}\n```\n\n# Versioning\n\nThe API is versioned. The current version is 2.0 (referenced as v2 in the endpoints).\n\n# Routes\n\nThe API endpoints are accessible through a route of the form: `https:///api//`.\n\nWhere:\n\n- `domain` is the domain to use, usually \"app.hubflo.com\"\n- `version` is the API version\n- `endpoint` is the endpoint name\n\nFor example, we will have: `https://app.hubflo.com/api/v2/pings`.\n\n# Request headers\n\nEvery request should include the header `Content-Type: application/json`, except for file uploads.\n\n# Requests and parameters\n\nThe API adheres to REST principles:\n\n- `GET` requests: read without modification\n- `POST` requests: create a new resource\n- `PATCH` requests: update an existing resource\n- `DELETE` requests: delete a resource\n\nThe parameters for `GET` requests should be sent via the query string of the request.\n\nThe parameters for `POST` and `PATCH` requests should be transmitted in the request body in a valid JSON format.\n\nThe parameters should follow the following formats:\n- `date`: \"YYYY-MM-DD\", for example: \"2021-10-21\"\n- `time`: \"H:m[:s]\", for example: \"10:30\"\n- `date-time`: \"YYYY-MM-DDThh:mm:ssZ\", which is the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations) format, using UTC\n\n# Response headers\n\nAs specified for each endpoint, the response headers contain:\n- `Content-Type`: the response content type\n- `X-Organization-ID`: your organization ID\n- `X-Rate-Limit` the maximum allowed requests in a given period\n- `X-Remaining-Requests`: the remaining requests count in the current period\n\n# Response format\n\nThe API only supports JSON format.\nAll responses sent by the API will contain the header `Content-Type: application/json` and their content is present in\nthe body in a JSON format to be de-serialized.\n\n# Rate limit\n\nThe use of the API is limited.\nYou can make a maximum of 1000 calls per minute.\nIf you exceed this limit, you receive a `429 - Too Many Requests` error and are blocked for one minute.\n\n# Pagination\n\nAll endpoints that return lists are paginated.\nIn general, any endpoint that returns a list can return an empty list.\n\nThe (optional) `page` parameter allows you to access a specific page.\n\nThe (optional) `per_page` parameter allows you to change the number of items on a given page.\nThe default value is 20 and it is limited to a maximum of 100.\n\n# Response codes\n\nThe API may return the following codes:\n\n| Code | Name | Description |\n| ---- | -------- | -------- |\n| `200` | Success | Success |\n| `201` | Created | Resource created |\n| `204` | No Content | Success but the response does not contain any data (e.g., deletion) |\n| `400` | Bad Request | The request is invalid |\n| `401` | Unauthorized | Authentication failed |\n| `403` | Forbidden | Insufficient rights to perform the requested action |\n| `404` | Not Found | The resource is not found |\n| `422` | Unprocessable Content | The transmitted data is malformed |\n| `429` | Too Many Requests | Too many requests have been made |\n| `500` | Internal Server Error | An internal server error occurred (the technical team is automatically notified) |\n\n# Errors\n\nWhen an error occurs, the response code informs you about what is happening.\nThe response body contains:\n- the status code,\n- the status name, a.k.a the error title,\n- a human readable message.\n\nSee the error schemas below.\n\n# Resources\n\nAll resources are identified by a unique ID that looks like this: \"16242d6f-a808-41b7-8c4d-fe29b9b3245f\".\n\nJSON data types are used at most: `string`, `number`, `float`, `object`, `array`, `boolean` and `null`.\nDates and datetimes attributes are serialized with UTC [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations) format.\n\n\n" servers: - url: https://app.hubflo.com description: The production API server - url: https://staging.hubflo.com description: The staging API server - url: http://localhost:3000 description: The local API server tags: - name: webhook paths: /api/v2/webhooks/{webhook_target_id}/activation: parameters: - name: webhook_target_id in: path required: true description: Webhook ID schema: type: string post: summary: Activates a webhook security: - bearer_auth: [] description: Activates a webhook so it resumes receiving events tags: - webhook responses: '201': description: Webhook activated headers: Content-Type: schema: type: string description: application/json; charset=utf-8 X-Organization-ID: schema: type: string description: The organization ID X-Rate-Limit: schema: type: integer description: Max allowed requests in the current period X-Remaining-Requests: schema: type: integer description: Remaining requests in the current period content: application/json: examples: example: value: id: 1f886b66-1026-45ae-8eee-4e0a0d51c510 event_names: - contact_created url: https://www.sample-1.com active: true created_at: '2026-07-17T13:10:11Z' '401': description: 'unauthorized: the Authorization header is missing or invalid' content: application/json: examples: example: value: status: 401 title: Unauthorized message: Invalid API token schema: $ref: '#/components/schemas/error_unauthorized' '404': description: 'not found: the resource is not found' content: application/json: examples: example: value: status: 404 title: Not Found message: Resource not found schema: $ref: '#/components/schemas/error_not_found' '429': description: 'too many requests: the user has reached the rate limit' content: application/json: examples: example: value: status: 429 title: Too Many Requests message: Rate limit reached. Please wait for a couple of minutes. schema: $ref: '#/components/schemas/error_too_many_requests' delete: summary: Deactivates a webhook security: - bearer_auth: [] description: Deactivates a webhook so it stops receiving events tags: - webhook responses: '200': description: Webhook deactivated headers: Content-Type: schema: type: string description: application/json; charset=utf-8 X-Organization-ID: schema: type: string description: The organization ID X-Rate-Limit: schema: type: integer description: Max allowed requests in the current period X-Remaining-Requests: schema: type: integer description: Remaining requests in the current period content: application/json: examples: example: value: id: e7b1996e-c76b-4dd0-b133-c91a74f176ff event_names: - contact_created url: https://www.sample-6.com active: false created_at: '2026-07-17T13:10:11Z' '401': description: 'unauthorized: the Authorization header is missing or invalid' content: application/json: examples: example: value: status: 401 title: Unauthorized message: Invalid API token schema: $ref: '#/components/schemas/error_unauthorized' '404': description: 'not found: the resource is not found' content: application/json: examples: example: value: status: 404 title: Not Found message: Resource not found schema: $ref: '#/components/schemas/error_not_found' '429': description: 'too many requests: the user has reached the rate limit' content: application/json: examples: example: value: status: 429 title: Too Many Requests message: Rate limit reached. Please wait for a couple of minutes. schema: $ref: '#/components/schemas/error_too_many_requests' /api/v2/webhooks/{webhook_target_id}/webhook_deliveries: get: summary: Retrieves the webhook deliveries security: - bearer_auth: [] description: Returns the deliveries sent to a webhook, most recent first, so their status and errors can be audited. Deliveries are retained for one month. tags: - webhook parameters: - name: page in: query required: false description: Page number example: 1 schema: type: number - name: per_page in: query required: false description: Number of items per page (max 100) example: 10 schema: type: number - name: webhook_target_id in: path required: true description: Webhook ID schema: type: string - name: errored in: query required: false description: Only return deliveries that errored (transport failure or HTTP status >= 400) schema: type: boolean responses: '200': description: Webhook deliveries retrieved headers: Content-Type: schema: type: string description: application/json; charset=utf-8 X-Organization-ID: schema: type: string description: The organization ID X-Rate-Limit: schema: type: integer description: Max allowed requests in the current period X-Remaining-Requests: schema: type: integer description: Remaining requests in the current period X-Page: schema: type: integer description: Current page number X-Per-Page: schema: type: integer description: Number of items per page X-Total-Pages: schema: type: integer description: Total number of pages X-Next-Page: schema: type: integer nullable: true description: Next page number X-Prev-Page: schema: type: integer nullable: true description: Previous page number X-Total-Count: schema: type: integer description: Total number of items content: application/json: examples: example: value: - id: cf626778-7d73-498b-9c5b-d2664cb70553 event_name: contact_created state: pending response_code: null payload: data: sample_payload webhook_delivery_id: cf626778-7d73-498b-9c5b-d2664cb70553 webhook_delivery_created_at: '2026-07-17T15:10:11.836+02:00' created_at: '2026-07-17T13:10:11Z' - id: 79fe5a96-079b-4a79-98df-3b1a7f7daadf event_name: contact_created state: pending response_code: null payload: data: sample_payload webhook_delivery_id: 79fe5a96-079b-4a79-98df-3b1a7f7daadf webhook_delivery_created_at: '2026-07-17T15:10:11.835+02:00' created_at: '2026-07-17T13:10:11Z' '401': description: 'unauthorized: the Authorization header is missing or invalid' content: application/json: examples: example: value: status: 401 title: Unauthorized message: Invalid API token schema: $ref: '#/components/schemas/error_unauthorized' '404': description: 'not found: the resource is not found' content: application/json: examples: example: value: status: 404 title: Not Found message: Resource not found schema: $ref: '#/components/schemas/error_not_found' '429': description: 'too many requests: the user has reached the rate limit' content: application/json: examples: example: value: status: 429 title: Too Many Requests message: Rate limit reached. Please wait for a couple of minutes. schema: $ref: '#/components/schemas/error_too_many_requests' /api/v2/webhooks: post: summary: Creates a webhook security: - bearer_auth: [] description: 'Creates a webhook that notifies the given `url` whenever one of the subscribed events occurs. Each delivery is signed so you can verify it originated from Hubflo. The request carries an `X-Hubflo-Signature` header containing the hex-encoded HMAC-SHA256 of the raw request body, computed with the webhook''s signing secret (returned as `secret` when the webhook is created). To verify a delivery, recompute the HMAC over the received body with your signing secret and compare it to the header value. Each delivery''s payload also includes a unique `webhook_delivery_id` (along with a `webhook_delivery_created_at` timestamp). Use it to deduplicate deliveries, since the same event may be delivered more than once. ' tags: - webhook parameters: [] responses: '201': description: Webhook created from a legacy singular event_name headers: Content-Type: schema: type: string description: application/json; charset=utf-8 X-Organization-ID: schema: type: string description: The organization ID X-Rate-Limit: schema: type: integer description: Max allowed requests in the current period X-Remaining-Requests: schema: type: integer description: Remaining requests in the current period content: application/json: examples: example: value: id: 15e32714-d549-4164-ab4e-c91104904308 event_names: - contact_created url: https://www.sample.com active: true created_at: '2026-07-17T13:10:12Z' secret: vcPcBkE29GH69uwi6e4r5uJf '401': description: 'unauthorized: the Authorization header is missing or invalid' content: application/json: examples: example: value: status: 401 title: Unauthorized message: Invalid API token schema: $ref: '#/components/schemas/error_unauthorized' '422': description: 'unprocessable content: the resource can''t be created' content: application/json: examples: example: value: status: 422 title: Unprocessable Content message: 'Validation failed: Event names must be filled in, Url must be filled in, Url is not a valid URL' schema: $ref: '#/components/schemas/error_unprocessable_content' '429': description: 'too many requests: the user has reached the rate limit' content: application/json: examples: example: value: status: 429 title: Too Many Requests message: Rate limit reached. Please wait for a couple of minutes. schema: $ref: '#/components/schemas/error_too_many_requests' requestBody: content: application/json: schema: type: object properties: event_names: type: array items: type: string enum: - authenticated_contact_added_to_workspace - comment_created - company_created - company_updated - contact_created - contact_invited - contact_signed_up - contact_updated - file_added_to_task - file_uploaded - file_uploaded_by_contact - folder_created - form_assignment_created - form_submission_completed - invoice_created - invoice_issued - invoice_overdue - invoice_paid - message_sent - message_sent_by_contact - project_stage_created - project_stage_updated - seal_submission_completed - seal_submission_created - task_completed - task_completed_by_contact - task_created - task_created_by_contact - task_overdue description: The events the webhook subscribes to. example: - contact_created url: type: string example: https://www.webhook.com required: - url required: true description: Webhook attributes /api/v2/webhooks/{id}: parameters: - name: id in: path required: true description: Webhook ID schema: type: string delete: summary: Deletes a webhook security: - bearer_auth: [] description: Deletes a webhook tags: - webhook responses: '204': description: Webhook deleted headers: X-Organization-ID: schema: type: string description: The organization ID X-Rate-Limit: schema: type: integer description: Max allowed requests in the current period X-Remaining-Requests: schema: type: integer description: Remaining requests in the current period content: application/json: examples: example: value: '' '401': description: 'unauthorized: the Authorization header is missing or invalid' content: application/json: examples: example: value: status: 401 title: Unauthorized message: Invalid API token schema: $ref: '#/components/schemas/error_unauthorized' '404': description: 'not found: the resource is not found' content: application/json: examples: example: value: status: 404 title: Not Found message: Resource not found schema: $ref: '#/components/schemas/error_not_found' '429': description: 'too many requests: the user has reached the rate limit' content: application/json: examples: example: value: status: 429 title: Too Many Requests message: Rate limit reached. Please wait for a couple of minutes. schema: $ref: '#/components/schemas/error_too_many_requests' components: schemas: error_not_found: description: A response describing a not found error type: object properties: status: type: integer example: 404 title: type: string example: Not Found message: type: string example: Resource not found required: - status - title - message error_unauthorized: description: A response describing an authentication error type: object properties: status: type: integer example: 401 title: type: string example: Unauthorized message: type: string example: API token not found required: - status - title - message error_too_many_requests: description: A response describing a rate limit error type: object properties: status: type: integer example: 429 title: type: string example: Too Many Requests message: type: string example: Rate limit reached. Please wait for a couple of minutes. required: - status - title - message error_unprocessable_content: description: A response describing a validation error type: object properties: status: type: integer example: 422 title: type: string example: Unprocessable Content message: type: string example: 'Validation failed: Title can''t be blank' required: - status - title - message securitySchemes: bearer_auth: type: http scheme: bearer x-readme: explorer-enabled: true proxy-enabled: true