Retrieve developer by slug

Returns the same full, detailed developer payload as GET /api/v2/clients/developers/{id}, but looked up by the developer's URL-friendly slug_name instead of its numeric id. Use this endpoint when you only have the slug — for example, when resolving SEO-friendly URLs, deep links shared externally, or cross-system references that carry the slug rather than the internal id. The response schema is identical to the id-based retrieve endpoint (RetrieveDeveloper). Returns 404 if no developer with the given slug_name exists.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

URL-friendly slug identifying the developer (lowercase ASCII letters, digits, and dashes). Assigned the first time the developer becomes active and stable thereafter — safe to embed in shareable URLs. See the slug_name field on ListDeveloper and RetrieveDeveloper responses.

Query Params
string
enum
Allowed:
Headers
string
required

Custom token for client authentication.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

401

Authentication credentials were not provided or are invalid.

403

You do not have permission to perform this action.

404

Not found.

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json