Consent Info

The Consent Info API lets your application check whether it has permission to process a user's personal data for a specific purpose and scope(s) before calling other Network as Code APIs. It returns a simple validity status and, when applicable, a URL that directs the user to the operator's consent capture channel.

This complements Consent and Identity Management, which covers B2B authorization requests and the list of available scopes for your organization. Consent Info is a runtime API you call per user to validate processing status at the moment you need it.

What does this feature do?

  1. Accepts the CAMARA scope(s) you intend to use, a DPV purpose, and a user identifier (phone_number / phoneNumber).
  2. Returns whether data processing is currently permitted (status_valid_for_processing / statusValidForProcessing).
  3. Optionally returns a capture URL (capture_url / captureUrl) so you can send the user to the operator to provide or renew consent.

Important: Consent Info does not capture consent in your application. When user action is required, the API can return the operator's secure capture URL (capture_url / captureUrl). Consent is collected in the API provider's environment, not delegated to your backend.

Terminology and acronymsheader link

What's behind this technology?header link

The Consent Info functionality follows CAMARA definitions, which is an open-source project within the Linux Foundation. Network as Code bridges the gap between your application and the Operator platform, making the connection seamless so you can retrieve consent status data. Once you have registered your application on the Network as Code Developer Portal, you can call Consent Info at runtime to check whether processing a user's data is permitted.

Last updated September 18, 2026