Update 0Gate branding

0Gate is the primary public integration path for hosted payment, ramp, and swap experiences. Keep secret-key operations on your server and hand only browser-safe values to the widget.

Co-branding lets the hosted widget render with your logo, colors, and name instead of the default Gate look. This endpoint writes those tokens from your server. It is a partial update: the supplied tokens are merged onto your current branding, so sending one field never wipes the rest.

Endpoint

Use it for

Set or change your co-branding tokens (logo, colors, brand name) from server-side code, without an admin step. The values you write are the same ones surfaced to the hosted widget via the embed bootstrap — set them here and they show up in the iframe.

Use this endpoint only for the partner-scoped resource it describes. Store the returned values alongside the request id and timestamps so support and reconciliation do not depend on browser callbacks alone.

Production rules

• Keep secret keys on your server. This endpoint requires an sk_* key; a publishable pk_* key is rejected.
• Send only the tokens you want to change — the update merges, it does not replace.
• Send only the documented tokens. Any other key is rejected with 400 (unknown keys are not silently ignored).
• Colors must be hex strings. The partner-facing contract is #RRGGBB. logo_url must be an absolute https URL.
• Branch on machine-readable fields and the request id, not on free-form text.
• Treat examples and placeholder ids as fake data only.

Merge semantics (PATCH, not replace)

A PATCH merges the tokens you send onto your current branding. Tokens you omit are left exactly as they were. To clear a token, set it explicitly to null.

Request body

All fields are optional. An empty body ({}) is a valid no-op — it changes nothing and returns your current branding. A PATCH merges the tokens you send onto your current branding (it does not replace), and unknown keys are rejected with 400. The body schema is BrandingUpdate.

Color format

The partner-facing contract for every color token is a 6-digit hex string, #RRGGBB (for example #F97316).

Response

Returns the full, resolved Branding object after the merge — the same shape as GET /branding. Every token is present; an unset token is null.

Examples

curl -X PATCH https://gate-api.0bit.app/v1/branding \
  -H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "primary_color": "#F97316",
    "brand_name": "Acme"
  }'

{
  "primary_color": "#F97316",
  "brand_name": "Acme"
}

{
  "object": "branding",
  "logo_url": "https://cdn.acme.example/logo.svg",
  "primary_color": "#F97316",
  "secondary_color": "#111827",
  "accent_color": "#22C55E",
  "brand_name": "Acme"
}

Rate limits

PATCH /v1/branding is limited to 30 requests per minute. Over the limit returns 429 with the unified error envelope; back off and retry.

Errors

All errors use the unified envelope and carry an X-Request-Id response header. Branch on code/type/statusCode, not on the free-form message.

{
  "type": "invalid_request",
  "code": "invalid_request",
  "message": "Example validation error using fake data.",
  "request_id": "req_test_000000000123",
  "doc_url": null,
  "statusCode": 400
}

Public boundary

This reference covers partner-scoped endpoint behavior, authentication, and the branding tokens you can read and write. Internal theme storage, administrative routes, and unsupported availability claims are outside the public API contract.

Related pages