Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hubflo contact API

The contact API from Hubflo — 4 operation(s) for contact.

Hubflo contact API is one of 28 APIs that Hubflo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include contact. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 6 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version v2.

Requests are made against 3 base URLs: https://app.hubflo.com, https://staging.hubflo.com, http://localhost:3000.

6 operations 4 paths 4 schemas 4 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v2
Base URL
https://app.hubflo.com/api/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Hubflo contact API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer_auth).

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

contact 6
GET
/api/v2/contacts/{contact_id}/workspaces
Retrieves the workspaces of the given contact. Only the first 100 tags of each workspace are returned
3 params → 200401404429
GET
/api/v2/contacts/{contact_id}/workspaces/{id}
Retrieves a workspace of the given contact. Only the first 100 tags of the workspace are returned
2 params → 200401404429
GET
/api/v2/contacts
Retrieves the contacts
9 params → 200401429
POST
/api/v2/contacts
Creates a contact
body → 201401429
GET
/api/v2/contacts/{id}
Retrieves a contact
1 param → 200401404429
PATCH
/api/v2/contacts/{id}
Updates a contact
1 param body → 200401404422429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are error_unprocessable_content (3 properties), error_too_many_requests (3 properties), error_unauthorized (3 properties), error_not_found (3 properties). Each schema is shown below with its type and property counts.

error_not_found
object
A response describing a not found error
3 properties 3 required
error_unauthorized
object
A response describing an authentication error
3 properties 3 required
error_too_many_requests
object
A response describing a rate limit error
3 properties 3 required
error_unprocessable_content
object
A response describing a validation error
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hubflo-contact-api-openapi.yml Raw ↑

Other APIs Hubflo publishes across the network.

Hubflo chat_room API
Hubflo comment API
Hubflo company API
Hubflo custom_field API
Hubflo custom_field_value API
Hubflo folder API
Hubflo form API
Hubflo invoice API
Hubflo invoicing_profile API
Hubflo item API
Hubflo member API
Hubflo message API