Integrate the Service Marketplace API

Authentication

Request a bearer token from the OAuth endpoint using the client credentials grant, then send it in the Authorization header of every call. Tokens are short-lived, so cache and refresh them server-side.

• POST /oauth/token - client credentials grant
• POST /v1/request/create - create a service request
• POST /v1/request/validate - validate duplicates
• Technical documentation and integration resources are provided to approved partners

Creating a request

Send form-encoded parameters with the category, location and description of the need. Approved partners can also submit base64 audio instead of text. Always validate first if your flow can produce repeated submissions.

Good practices

Keep partner credentials server-side, never in a browser or mobile bundle. Handle rate limits with exponential backoff, log the returned identifiers, and treat validation as part of the happy path rather than an optional extra.

Frequently asked questions

Which content type does the create endpoint expect?

application/x-www-form-urlencoded, with a bearer token in the Authorization header.

Where is the full documentation?

Technical documentation and integration resources, including an OpenAPI specification and a Postman collection, are provided directly to approved partners during onboarding.

Is the OpenAPI specification public?

No. It is part of our private partner resources and is shared with approved partners, together with a Postman collection, to speed up integration.