Skip to content

source-twilio: Fix subaccount behavior #4441

@jonwihl

Description

@jonwihl

There are two main types of API keys used by Twilio: main and standard [ref] (https://www.twilio.com/docs/usage/requests-to-twilio?_gl=1*bx7bec*_gcl_au*MTk2OTg4MTMyNi4xNzc3Mzg1NTE3*_ga*MTE2Nzk1MzE4NS4xNzc3Mzg1MjA3*_ga_RRP8K4M4F3*czE3NzczODc3NTAkbzIkZzEkdDE3NzczOTA2MzMkajUzJGwwJGgw#using-api-keys-recommended)

A standard key is unable to access certain streams like Accounts and Keys while a main key is unable to access streams for subaccounts. If a user has sub accounts and uses a main api key, it will fail on subsequent calls when it tries to access a resource for a subaccount (api.twilio.com/Accounts//Calls). A standard key will fail at publish with an unauthorized.

Most users with subaccounts want to use a main API key and only capture endpoints using their main account id. We would need to add a configuration option (Capture subaccounts) that will only ever use the account id defined in the configuration for making requests

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions