MCP is live.Set upAsk the community
OmniDimension
Dashboard
DocumentationAPI referenceSDKsMCP
Reseller clients

Update user expiry

Set or remove the expiry date on a child user. The user must belong to a child organization of your reseller.

Reseller accounts only. Request access.

POST/reseller/users/expiry
Body
2 fields
·

ID of the child user to update.

Expiry date in YYYY-MM-DD format. Omit or pass null to remove the expiry.

curl -X POST 'https://backend.omnidim.io/api/v1/reseller/users/expiry' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "user_id": 1234,
  "expiry_date": "2026-12-31"
}'
Example response
synthetic
{
  "success": true,
  "message": "User expiry date updated successfully",
  "user_id": 1234,
  "expiry_date": "2026-12-31"
}

Authorization

BearerAuth
headerAuthorizationBearer <token>

Bearer token authentication. Obtain your API key from the OmniDimension dashboard.

Request Body

application/json
user_id*integer

ID of the child user to update.

expiry_date?string

Expiry date in YYYY-MM-DD format. Omit or pass null to remove the expiry.

Formatdate

Response body

application/json

Response Body

Expiry updated.

application/json
success?boolean
message?string
user_id?integer
expiry_date?string
Formatdate

Release a client

End your relationship with one direct client, for good. One-way: unlike blocking, a release cannot be undone.

Issue a client API key

Issue a named API key for a user in one of your client organizations. The secret is in this response only, so store it now. No listing shows it again. To rotate a key, issue a new one, switch the integration to it, then revoke the old one.