# Create configuration card link for a source
Source: https://developer.portable.io/api-reference/configuration-cards/create-configuration-card-link-for-a-source

/api-spec-v2.yaml post /v2/sources/{id}/configuration_cards
Create a new configuration card link for a given source



# Get destination spec
Source: https://developer.portable.io/api-reference/destination-specs/get-destination-spec

get /v2/destinationspecs/{name}
Get a destination spec by name



# List destination specs
Source: https://developer.portable.io/api-reference/destination-specs/list-destination-specs

get /v2/destinationspecs
List all supported destination specs



# Create a destination
Source: https://developer.portable.io/api-reference/destinations/create-a-destination

post /v2/destinations
Create a new destination



# Delete destination
Source: https://developer.portable.io/api-reference/destinations/delete-destination

delete /v2/destinations/{id}
Delete an existing destination



# Get destination
Source: https://developer.portable.io/api-reference/destinations/get-destination

get /v2/destinations/{id}
Get a destination by ID



# List destinations
Source: https://developer.portable.io/api-reference/destinations/list-destinations

get /v2/destinations
List all the destinations for the given user. A destination is where the data from a source gets loaded into.



# Update destination
Source: https://developer.portable.io/api-reference/destinations/update-destination

patch /v2/destinations/{id}
Update an existing destination



# Verify if a destination is properly configured
Source: https://developer.portable.io/api-reference/destinations/verify-if-a-destination-is-properly-configured

get /v2/destinations/{id}/verify
Use this endpoint to validate the properties for the specified destination. If any required property is missing, the response will include a relevant error message. If all required properties are present, it attempts to establish a connection with the destination and returns a status message indicating whether the connection was successful.
The response is an array of check messages. Each element in the array includes two fields: `isError`, a boolean flag, and `message`, a string. The `isError` field should be used to distinguish between error messages and informational messages. See the provided example for more details.
All this process is performed synchronously, so it may take a few seconds to complete. There is also a timeout of 10 seconds for the whole process.




# Cancel a running flow
Source: https://developer.portable.io/api-reference/flows/cancel-a-running-flow

post /v2/flows/{id}/cancel
Cancels an ongoing run of a flow by flow ID. If the flow is not running, this operation has no effect. You can use `/v2/flows/{id}/status` to check the status of this run.




# Create flow
Source: https://developer.portable.io/api-reference/flows/create-flow

post /v2/flows
Create a new flow



# Delete flow
Source: https://developer.portable.io/api-reference/flows/delete-flow

delete /v2/flows/{id}
Delete an existing flow



# Get flow
Source: https://developer.portable.io/api-reference/flows/get-flow

get /v2/flows/{id}
Get a flow by ID



# Get flow run attempts
Source: https://developer.portable.io/api-reference/flows/get-flow-run-attempts

get /v2/flows/{id}/run
Get a flow's run attempts by flow ID



# Get flow status
Source: https://developer.portable.io/api-reference/flows/get-flow-status

get /v2/flows/{id}/status
Get a flow's status by flow ID. Use this endpoint to check whether a flow is running or not, or get details about the flow's last run.
The response includes the flow's lifecycle status, disposition, and the status of the resources involved in the




# List flows
Source: https://developer.portable.io/api-reference/flows/list-flows

get /v2/flows
List all the existing flows. A flow is a combination of a source and an environment.



# Run a flow
Source: https://developer.portable.io/api-reference/flows/run-a-flow

post /v2/flows/{id}/run
Initiates a run of a flow by flow ID. The flow will be run asynchronously. Use `/v2/flows/{id}/status` to check the status of this run.




# Update flow
Source: https://developer.portable.io/api-reference/flows/update-flow

patch /v2/flows/{id}
Update an existing flow



# Get source spec
Source: https://developer.portable.io/api-reference/source-specs/get-source-spec

get /v2/sourcespecs/{name}
Get a source spec by name



# List source specs
Source: https://developer.portable.io/api-reference/source-specs/list-source-specs

get /v2/sourcespecs
List all source specs



# Create source
Source: https://developer.portable.io/api-reference/sources/create-source

post /v2/sources
Create a new source



# Delete source
Source: https://developer.portable.io/api-reference/sources/delete-source

delete /v2/sources/{id}
Delete an existing source



# Discover dynamic resolvers for a source
Source: https://developer.portable.io/api-reference/sources/discover-dynamic-resolvers-for-a-source

/api-spec-v2.yaml post /v2/sources/{id}/discover
Starts an asynchronous process to discover dynamic resolvers for the specified source. This process runs in the background. To check the status of the discovery process and retrieve the discovered resources, poll the `GET /v2/sources/{id}/resolvers` endpoint.




# Get discovered resolvers for a source
Source: https://developer.portable.io/api-reference/sources/get-discovered-resolvers-for-a-source

/api-spec-v2.yaml get /v2/sources/{id}/resolvers
Returns the list of discovered resolvers for the specified source, including both static (spec-defined) and dynamic resolvers found during the last discovery or extraction process.




# Get source
Source: https://developer.portable.io/api-reference/sources/get-source

get /v2/sources/{id}
Get a source by ID



# List sources
Source: https://developer.portable.io/api-reference/sources/list-sources

get /v2/sources
List all the sources. A source is an instantiation of a source spec.



# Update source
Source: https://developer.portable.io/api-reference/sources/update-source

patch /v2/sources/{id}
Update an existing source



# Verify if a source is properly configured
Source: https://developer.portable.io/api-reference/sources/verify-if-a-source-is-properly-configured

get /v2/sources/{id}/verify
Use this endpoint to validate the properties for the specified source. If any required property is missing, the response will include a relevant error message. If all required properties are present, it attempts to establish a connection with the source's API servers and returns a status message indicating whether the connection was successful.
The response is an array of check messages. Each element in the array includes two fields: `isError`, a boolean flag, and `message`, a string. The `isError` field should be used to distinguish between error messages and informational messages. See the provided example for more details.
All this process is performed synchronously, so it may take a few seconds to complete. There is also a timeout of 10 seconds for the whole process.




# Create webhook trigger
Source: https://developer.portable.io/api-reference/webhooks/create-webhook-trigger

/api-spec-v2.yaml post /v2/workflows/{id}/webhooks
Create a new webhook trigger for a workflow



# Delete webhook trigger
Source: https://developer.portable.io/api-reference/webhooks/delete-webhook-trigger

/api-spec-v2.yaml delete /v2/workflows/{id}/webhooks/{webhook_trigger_id}
Delete a webhook trigger



# Get webhook trigger
Source: https://developer.portable.io/api-reference/webhooks/get-webhook-trigger

/api-spec-v2.yaml get /v2/workflows/{id}/webhooks/{webhook_trigger_id}
Get a webhook trigger by ID



# List webhook triggers
Source: https://developer.portable.io/api-reference/webhooks/list-webhook-triggers

/api-spec-v2.yaml get /v2/workflows/{id}/webhooks
List all webhook triggers for a workflow



# Update webhook trigger
Source: https://developer.portable.io/api-reference/webhooks/update-webhook-trigger

/api-spec-v2.yaml patch /v2/workflows/{id}/webhooks/{webhook_trigger_id}
Update a webhook trigger (currently only status can be updated)



# Cancel workflow run
Source: https://developer.portable.io/api-reference/workflows/cancel-workflow-run

/api-spec-v2.yaml post /v2/workflows/{id}/cancel
Cancel a workflow run



# Create workflow
Source: https://developer.portable.io/api-reference/workflows/create-workflow

/api-spec-v2.yaml post /v2/workflows
Create a new workflow



# Delete workflow
Source: https://developer.portable.io/api-reference/workflows/delete-workflow

/api-spec-v2.yaml delete /v2/workflows/{id}
Delete a workflow



# Get workflow
Source: https://developer.portable.io/api-reference/workflows/get-workflow

/api-spec-v2.yaml get /v2/workflows/{id}
Get a workflow by ID



# Get workflow status
Source: https://developer.portable.io/api-reference/workflows/get-workflow-status

/api-spec-v2.yaml get /v2/workflows/{id}/status
Get a workflow's status by workflow ID. Use this endpoint to check whether a workflow is running or not, or get details about the workflow's last run.




# List workflow runs
Source: https://developer.portable.io/api-reference/workflows/list-workflow-runs

/api-spec-v2.yaml get /v2/workflows/{id}/runs
List runs for a workflow



# List workflows
Source: https://developer.portable.io/api-reference/workflows/list-workflows

/api-spec-v2.yaml get /v2/workflows
List all workflows



# Run workflow
Source: https://developer.portable.io/api-reference/workflows/run-workflow

/api-spec-v2.yaml post /v2/workflows/{id}/run
Trigger a workflow run



# Update workflow
Source: https://developer.portable.io/api-reference/workflows/update-workflow

/api-spec-v2.yaml patch /v2/workflows/{id}
Update a workflow