Skip to content
Changelog

Report a bug

Planly integration: operations for AI agents

Planly connects to Type.com as an integration. This page lists the 23 operations documented for Claude and Codex in Type.com: 9 read, 8 write, 6 destructive.

About Planly

All-in-one social media management tool for scheduling and managing content across multiple platforms

Categories: Marketing & Social

How to connect Planly to Type.com

Access
Organization connection: one shared account for the workspace.
MCP
Selected social-publishing operations are not available through Type’s MCP server. Other operations remain available through MCP, subject to your connection’s permissions. These MCP restrictions do not apply within Type.

To add the connection, follow the steps in Space connections.

Documented operations

23 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

23 operations listed.

Artificial Intelligence

  • Read

    Get Available Credits

    Get available AI credits left in a team.

    GET /api/v2/ai/credits

  • Write

    Complete Prompt

    Complete text prompt.

    POST /api/v2/ai/complete

Channels

  • Read

    List Channels

    List Channels.

    POST /api/v2/channels/list

  • Destructive

    Delete Channel

    Delete the connected channel identified by id.

    GET /api/v2/channels/delete

Media

  • Read

    List Media

    This endpoint retrieves medias in a specified team.

    POST /api/v2/media/list

  • Write

    Start Upload

    To initiate the upload process for your media file to Planly, call the start-upload endpoint. The fields teamId and contentLength are mandatory. Additionally, you must provide at least one of the contentType or fileName fields. If both contentType and fileName are provided, only contentType will be honored. As a response, this endpoint returns a unique mediaId and a pre-signed uploadUrl to which you can upload your file using a PUT request. Important : The file size ( contentLength ) will be validated during the upload. For example, if you specify a size of 10MB but attempt to upload a 15MB file, the upload will be rejected.

    POST /api/v2/media/start-upload

  • Write

    Finish Upload

    To complete the upload process for your media file, call the finish-upload endpoint. This step is necessary to confirm that the file was successfully uploaded and to finalize its storage on the server. You must provide the mediaId that was returned in the response of the start-upload request. As a response, this endpoint returns metadata for the uploaded file, including the file's direct URL, resolution, duration (for videos), and creation details.

    POST /api/v2/media/finish-upload

  • Write

    Import Media from URL

    The response is identical to /media/finish-upload To import media from URL to your team use this endpoint. Supported media content types are video/mp4 , image/png , image/jpeg , image/webp .

    POST /api/v2/media/import-from-url

  • Destructive

    Delete Media

    Delete the media entries identified by the supplied array of IDs.

    POST /api/v2/media/delete

Pinterest

  • Read

    Get Board List

    Returns the list of boards for a connected Pinterest channel. Use this to get board IDs when creating schedules with Pinterest options (the boardId field is required when publishing).

    POST /api/v2/pinterest/get-board-list/:channelId

Schedule Groups

  • Read

    List Schedule Groups

    List a team’s schedule groups, optionally filtering by group IDs, channels and status.

    POST /api/v2/schedule-groups/list

  • Write

    Create/Update Schedule Group

    Providing an id will update the existing group, while omitting it will create a new group.

    POST /api/v2/schedule-groups/create

  • Destructive

    Delete Schedule Groups

    Delete schedule groups by their IDs. All schedules within the groups will also be deleted.

    POST /api/v2/schedule-groups/delete

Schedules

  • Read

    List Schedules

    This endpoint retrieves schedules in a specified team. For pagination, include next field returned from response in next request's pagination.cursor field.

    POST /api/v2/schedules/list

  • Write

    Create Schedule

    The response is identical to /schedule-groups/create

    POST /api/v2/schedules/create

Teams

  • Read

    List Teams

    This endpoint retrieves all teams that you belong.

    POST /api/teams/list

  • Read

    Get Team

    Retrieve team details, member and channel counts, and account permissions by team ID.

    POST /api/v2/team/get

  • Read

    List Team Users

    List users belonging to the team identified by id.

    POST /api/v2/team/users

  • Write

    Create Team

    Create a team with the supplied name.

    POST /api/v2/team/create

  • Write

    Edit Team

    Update a team’s name using its team ID.

    POST /api/v2/team/edit

  • Destructive

    Delete Team

    Delete the team identified by id.

    POST /api/v2/team/delete

  • Destructive

    Transfer Team Ownership

    Transfer ownership of the specified team to the supplied user ID.

    POST /api/v2/team/transfer-ownership

  • Destructive

    Remove User from Team

    Remove the supplied user from the specified team.

    POST /api/v2/team/users/remove

See How connections work for access and permissions, or browse all integrations.

Reference date: October 28, 2026. Planly API docs.