Create Custom Service Endpoint

Create a tenant-scoped custom Descope outbound app.

Returns the app_id so the frontend can immediately kick off the connect flow (OAuth) or surface the API key form. Presets do not pass through this endpoint — their app ids come straight from GET /integrations/providers.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

customobjectRequired

Tenant-scoped custom integration spec.

The frontend owns slug derivation (live preview matches what’s stored). The backend treats slug as authoritative input and only validates its shape — it never re-derives. name is the free-form human label and is allowed to contain anything reasonable.

Response

Successful Response

app_idstring

namestring

slugstring

auth_methodenum

Shape of the Descope outbound app backing this integration.

Limited to the two underlying Descope app types: OAUTH (oidc) and API_KEY (custom_api_key). The injection style for an API-key integration (bearer / basic / custom header) is configured on the GatewayRule, not the integration itself, so any number of rules can re-use the same stored credential with different injection conventions.

Allowed values:

Errors

400

Bad Request Error

401

Unauthorized Error

422

Unprocessable Entity Error

1	curl -X POST /integrations/custom-services \
2	-H "Authorization: Bearer <api_key>" \
3	-H "Content-Type: application/json" \
4	-d '{
5	"custom": {
6	"name": "Acme Payment Gateway",
7	"slug": "acme-payments"
8	}
9	}'

1	{
2	"app_id": "app_9f8b7c6d5e4a3b2c1d0e",
3	"name": "Acme Payment Gateway",
4	"slug": "acme-payments",
5	"auth_method": "oauth"
6	}