Content Snare

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has state: "READY", skip to Step 2.

#### 1b. Wait for the connection to be ready

If the connection is in BUILDING state, poll until it's ready:

npx @membranehq/cli connection get  --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

The resulting state tells you what to do next:

After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get --json to check if the state moved to READY.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Requests | list-requests | Retrieve a list of all requests in Content Snare | | List Clients | list-clients | Retrieve a list of all clients in Content Snare | | List Team Members | list-team-members | Retrieve a list of all team members in the account | | Get Request | get-request | Retrieve details of a specific request by ID | | Get Client | get-client | Retrieve details of a specific client by ID | | Get Team Member | get-team-member | Retrieve details of a specific team member by ID | | Create Request | create-request | Create a new content request in Content Snare | | Create Client | create-client | Create a new client in Content Snare | | Create Team Member | create-team-member | Create a new team member in the account | | Update Request | update-request | Update an existing request's information | | Update Client | update-client | Update an existing client's information | | Update Team Member | update-team-member | Update an existing team member's information | | Delete Request | delete-request | Delete a request from Content Snare | | Delete Client | delete-client | Delete a client from Content Snare | | Delete Team Member | delete-team-member | Delete a team member from the account | | Create Page | create-page | Create a new page within a request | | Create Section | create-section | Create a new section within a page | | List Request Templates | list-request-templates | Retrieve a list of all request templates | | List Page Templates | list-page-templates | Retrieve a list of all page templates | | List Section Templates | list-section-templates | Retrieve a list of all section templates |

Running actions

membrane action run  --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run  --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Content Snare API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

membrane request CONNECTION_ID /path/to/endpoint

Common options:

| Flag | Description | |------|-------------| | -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET | | -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" | | -d, --data | Request body (string) | | --json | Shorthand to send a JSON body and set Content-Type: application/json | | --rawData | Send the body as-is without any processing | | --query | Query-string parameter (repeatable), e.g. --query "limit=10" | | --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |

Best practices