Skip to main content
Tape API

Coming from the Podio API

Move an integration from the Podio API to the Tape API with the same concepts and familiar endpoints.

Tape and Podio share their building blocks: organizations, workspaces, apps, fields, views, and webhooks. Most scripts need new names, a new base URL, and a new token.

Before you begin​

You need a Tape organization with your apps in it. Moving a whole Podio organization? Use the free Zooli Migration Tool first, as described in Migrate to Tape, then point your code at Tape.

The migration gives your apps, fields, and records new IDs. Replace the old IDs and external_id values in your scripts. The Developer view of each app lists the new IDs and slugs.

Tape builds each field slug from the field name, with underscores instead of hyphens. A Podio external_id like due-date usually becomes due_date.

Send every request to https://api.tapeapp.com. The API sends and receives JSON.

Map the concepts​

Podio APITape APINote
itemrecord
item_idrecord_id
app_item_idapp_record_idFind a record by it with a metadata filter.
external_id on an item–Records have no external_id. Store it in a text field and filter by it.
external_id on a fieldslug on a fieldRecords still return it as external_id. See Podio field types.
item fieldsrecord fieldsWrite values as an object keyed by field ID or slug. The value format depends on the field type. See Field values.
space, space_idworkspace, workspace_idSee Workspace.
organizationorganizationA token works in one organization. See Organization.
contact–No Tape endpoint. Use users for people in your organization and records for external contacts.
app, app fieldapp, fieldChange fields with Update an app.
calculation fieldcalculation fieldJavaScript with plain field names, like First_name instead of @First name. See the syntax table.
viewviewSee View.
filterfilterSend filters as an array of filter objects, each with a field ID (not a slug) and a match_type. Send sort_by, sort_desc, limit and cursor in the query string, not in the body. Date ranges and categories: see Filter.
hookwebhookSame verification flow. See Move your webhooks.
flow, Podio Workflow Automation (Globiflow)automationBuild them in the automation editor or with the Automation API. See Move your flows.
app authentication, OAuthpersonal access token, OAuthSee Switch authentication.
commentrecord commentSee Record comment.
filefileUpload first, then attach the file ID to a record or comment. See File.
revisionrecord revisionSee Record revision.
grantrecord permissionsSee Record permissions.
subscriptionfollowSee Unfollow all records in a database app.
task–No Tape endpoint. See Good to know.
rate limitrequest limitsCredits per minute. See Plan for request limits.
offsetcursorNo offset. Pass the cursor of the previous page to get the next one. See Pagination.

Find the matching endpoint​

TaskPodio APITape API
Create a recordPOST /item/app/{app_id}/POST /v1/record/app/{app_id}
Retrieve a recordGET /item/{item_id}GET /v1/record/{record_id}
Update a recordPUT /item/{item_id}PUT /v1/record/{record_id}
Delete a recordDELETE /item/{item_id}DELETE /v1/record/{record_id}
Records of a database appGET /item/app/{app_id}/GET /v1/record/app/{app_id}
Filter recordsPOST /item/app/{app_id}/filter/POST /v1/record/filter/app/{app_id}
Records of a viewPOST /item/app/{app_id}/filter/{view_id}/GET /v1/record/view/{view_id}
Create many records–POST /v1/record/app/batch/{app_id}
Related recordsGET /item/{item_id}/reference/POST /v1/record/app/{app_id}/ref/{ref_app_id}
Record revisionsGET /item/{item_id}/revision/GET /v1/record/{record_id}/revision
Add a commentPOST /comment/item/{item_id}/POST /v1/comment/record/{record_id}
Upload a filePOST /file/POST /v1/file/upload
Attach a filePOST /file/{file_id}/attachSend the file ID in an attachment field value
Retrieve an appGET /app/{app_id}GET /v1/app/{app_id}
Apps of a workspaceGET /app/space/{space_id}/GET /v1/app/workspace/{workspace_id}
Create a viewPOST /view/app/{app_id}/POST /v1/view/app/{app_id}
Create a workspacePOST /space/POST /v1/workspace
Workspace membersGET /space/{space_id}/member/GET /v1/workspace/{workspace_id}/member
SearchPOST /search/GET /v1/search
Create a webhookPOST /hook/{ref_type}/{ref_id}/POST /v1/hook/app/{app_id}
Current userGET /userGET /v1/user

Switch authentication​

Replace the Podio header Authorization: OAuth2 <token> with a bearer token:

curl https://api.tapeapp.com/v1/user \
-H "Authorization: Bearer $TAPE_TOKEN"

Choose the credential that matches your Podio flow:

Podio flowUse in Tape
Server-side flow, for your own scriptsPersonal access token. It can also act on a user's behalf when that user creates it
Server-side flow, for a product other Tape users connectOAuth with PKCE and a client registered by Tape
Client-side flowOAuth with PKCE and a public client registered by Tape, no client secret needed
Username and password flowPersonal access token
App authenticationPersonal access token with its content access limited to that app and only the capabilities your script needs. Tape has no token per app. Records, comments and revisions show the token's user as the author, so create the token from a dedicated user for the integration. See Attribution

Move your webhooks​

Webhooks verify the same way. Tape sends type hook.verify with a code, and your endpoint calls Validate hook verification.

What changes:

  • Tape sends hook.verify right after you create a webhook. Call Request hook verification only if your endpoint missed it.
  • Tape sends a JSON body, not form parameters.
  • Events start with record. instead of item., for example record.create. Tape adds record.restore.
  • The payload carries record_id and revision_id instead of item_id and item_revision_id.
  • Webhooks apply to a whole app. To react to one field, use an automation with a filter.

A minimal handler in Node.js:

app.post('/tape-webhook', async (req, res) => {
const { type, hook_id, code, record_id } = req.body;
res.sendStatus(200);
if (type === 'hook.verify') {
await fetch(`https://api.tapeapp.com/v1/hook/${hook_id}/verify/validate`, {
method: 'POST',
headers: { Authorization: `Bearer ${process.env.TAPE_TOKEN}`, 'Content-Type': 'application/json' },
body: JSON.stringify({ code }),
});
}
if (type === 'record.create') {
// For example, create a follow-up task for a new lead.
}
});
How do you avoid endless loops?

Update a record from a webhook with hook=false, as in the Podio API, plus workflow=false, because hook=false doesn't stop automations. Add silent=true to skip notifications. See Avoid endless loops.

Move your flows​

A Podio flow or a Globiflow flow becomes an automation in one app. Field references use the field_id, not the external_id. Find the action for each flow step in Coming from Podio.

In Podio, the flow starts when …Tape trigger
An item is created, updated or deletedrecord_created, record_updated, record_deleted
A comment is addedrecord_comment_or_reply_created
A date in a field arrivesdate_field_arrived
A schedule is dueperiodic
A hook or webhook comes inwebhook_received
Another flow calls itautomation_called
Someone starts it by hand or with a buttonAny trigger with manual-run, or a weblink with weblink_clicked

Plan for request limits​

Tape counts credits per minute instead of calls per hour. All credentials of a user share one budget, so more tokens don't add throughput.

Each response carries rate limit headers. After a 429, wait the seconds in Retry-After before you retry. See Request limits.

Good to know​

  • Tape has no client libraries for PHP or Ruby. Call the API over HTTPS from any language.
  • Tasks, status updates, and the activity stream have no Tape endpoints. Use a checklist field and record revisions instead.
  • Tape adds endpoints the Podio API doesn't have: batch create and update, restore a record, the Automation API, and the Tape MCP server.

Next steps​