Unlike the public
/metadata.json, this authenticated endpoint returns capabilities specific to the requesting OCID based on your service preferences or partnership agreements.Use Cases
Use this endpoint to provide differentiated access:- Preferred partners - Grant additional capabilities to strategic partners
- Restricted access - Limit certain OCIDs to specific operations
- Custom settlement - Offer different settlement options per partner
Example Response
Authentication
Verify the request signature using the caller’s public key from their/metadata.json endpoint. See Request Authentication for details.