PUTActivate Service for User

Activate a specific service (by service code) for one of your agents/retailers.

PUT/admin/network/agent/{user_code}/service/{service_code}/activate

Enables a service for the given agent so they can begin transacting on it. The agent is identified by their user_code and the service by its service_code, both supplied as path parameters. After activation, confirm the status with the Get User's Services API.

Path parameters

Field	Type	Required	Description
`user_code`	string	required	Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your userse.g. 20810200
`service_code`	string	required	Unique code of the service to activate for the user. See the service codes reference.e.g. 53

user_codestringRequired

Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users

example: 20810200

service_codestringRequired

Unique code of the service to activate for the user. See the service codes reference.

example: 53

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

Headers

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.