Skip to main content
Use mudraid-sdk in the application making requests. Configure MachineAgent with the linked client, signing key and approved resource grant.
Configure a linked OAuth client, signing key and approved resource grant as shown in the quickstart, then:
The SDK signs a client assertion locally, exchanges it at the configured token endpoint, caches the returned access token, and attaches it to resource requests. The platform verifies the token and enforces resource scopes. Linking a client alone does not approve a grant.

​
Requests and recovery

get, head, options, post, put, patch and delete return requests.Response objects. Choose request timeouts explicitly. Configure a separate client for each resource/scoped identity. A consequential request with an uncertain outcome is not blindly replayed. Recovery depends on the method and a server-enforced idempotency key; token refresh does not guarantee every request can safely be retried. Handle MudraIDExecutionUnknownError by reconciling the operation first. Use a custom signer= for externally managed signing, or install the v2 extra for the built-in signer. The private key remains local. Token-endpoint redirects are refused, and production token exchange requires HTTPS. Resource and token connections use separate sessions. Close the client when finished; caller-owned sessions and token managers remain your responsibility. Select the intended process configuration explicitly with MachineAgent.from_env(prefix). See Configuration, Errors, and the platform middleware.