Knowledge · API

    API clients, scopes and agent access

    How registered API clients, scopes and per-client revocation keep external agents as narrow consumers instead of general-purpose operators.

    What is an API client scope?

    A scope is the declared slice of an interface a registered client may use. It narrows what the client can request, independently of what the acting user is allowed to do. The effective permission is the intersection of the two, which is what keeps an external agent narrow.

    Key takeaways

    • A client is registered and named; a scope limits what it may request.
    • Effective access is the intersection of client scope and user permission.
    • Per-client revocation contains a compromise to one integration.
    • Scopes should be granted per use case, not per convenience.
    • An unscoped client is a general-purpose key with extra steps.

    Client, scope and user are three separate things

    • Client: the named application connecting, registered and approved.
    • Scope: the subset of the interface that client may call.
    • User: the person the calls are made on behalf of, with their own permissions.
    • Effective access: only what all three permit.

    Why external agents stay consumers

    An assistant connected through a scoped client sees a deliberately narrow surface. It cannot reach administrative functions simply because the person who connected it happens to be an administrator, because the client's scope never included them. That separation is what makes an external integration safe to grant and cheap to revoke.

    Operational hygiene

    • One client per integration, so revocation is surgical.
    • Review connected clients on the same cadence as user access.
    • Prefer short-lived tokens with refresh over long-lived secrets.
    • Log which client performed each action, alongside the user.

    Where URBLD fits

    URBLD treats external agent connections as registered clients approved on a consent screen and acting on behalf of one user, with administrative and privileged surfaces excluded from the agent-facing action catalog entirely rather than gated behind the connecting user's role.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in API

    The word everyone uses and few can define.

    Browse API
    Share this page