Svix · Arazzo Workflow

Svix Resend a Failed Message Attempt

Version 1.0.0

Find a failing delivery attempt for a message and resend it to its endpoint.

1 workflow 1 source API 1 provider
View Spec View on GitHub WebhookWebhooks As A ServiceWebhook DeliveryWebhook SendingEvent-DrivenEventingMessagingPub-SubStreamingIngestIntegrationReliabilityRetriesDeliverabilitySigningVerificationHMACStandard WebhooksMulti-TenantMulti-RegionEnterpriseSoftware-as-a-ServiceDeveloper PlatformRESTSOC 2HIPAAPCI DSSGDPROpen-SourceRustPolyglot SDKTerraformCLIArazzoWorkflows

Provider

svix

Workflows

resend-failed-attempt
Locate a failed delivery attempt for a message and resend it.
Lists the attempts for a message filtered to the failing status, and when a failed attempt exists, resends the message to the endpoint that failed.
2 steps inputs: appId, msgId outputs: failedEndpointId
1
listFailedAttempts
List the delivery attempts for the message filtered to the failed status. Returns 200 with a paged attempt list.
2
resendWebhook
Resend the message to the endpoint whose attempt failed, creating a new delivery attempt. Returns 202 Accepted.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Svix Resend a Failed Message Attempt
  summary: Find a failing delivery attempt for a message and resend it to its endpoint.
  description: >-
    When a single webhook delivery fails, an operator often wants to retry it to
    a specific endpoint. This workflow lists the delivery attempts for a
    message, branches on whether any failed attempt is present, and resends the
    message to the endpoint that failed. Every step spells out its request
    inline so the flow can be read and executed without opening the underlying
    OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: messageAttemptApi
  url: ../openapi/svix-message-attempt-api-openapi.yml
  type: openapi
workflows:
- workflowId: resend-failed-attempt
  summary: Locate a failed delivery attempt for a message and resend it.
  description: >-
    Lists the attempts for a message filtered to the failing status, and when a
    failed attempt exists, resends the message to the endpoint that failed.
  inputs:
    type: object
    required:
    - appId
    - msgId
    properties:
      appId:
        type: string
        description: The id or uid of the application owning the message.
      msgId:
        type: string
        description: The id or uid of the message whose attempts are inspected.
  steps:
  - stepId: listFailedAttempts
    description: >-
      List the delivery attempts for the message filtered to the failed status.
      Returns 200 with a paged attempt list.
    operationId: v1.message-attempt.list-by-msg
    parameters:
    - name: app_id
      in: path
      value: $inputs.appId
    - name: msg_id
      in: path
      value: $inputs.msgId
    - name: status
      in: query
      value: 2
    - name: limit
      in: query
      value: 1
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      failedEndpointId: $response.body#/data/0/endpointId
    onSuccess:
    - name: hasFailure
      type: goto
      stepId: resendWebhook
      criteria:
      - context: $response.body
        condition: $.data.length > 0
        type: jsonpath
    onFailure:
    - name: noFailures
      type: end
      criteria:
      - condition: $statusCode == 200
  - stepId: resendWebhook
    description: >-
      Resend the message to the endpoint whose attempt failed, creating a new
      delivery attempt. Returns 202 Accepted.
    operationId: v1.message-attempt.resend
    parameters:
    - name: app_id
      in: path
      value: $inputs.appId
    - name: msg_id
      in: path
      value: $inputs.msgId
    - name: endpoint_id
      in: path
      value: $steps.listFailedAttempts.outputs.failedEndpointId
    successCriteria:
    - condition: $statusCode == 202
  outputs:
    failedEndpointId: $steps.listFailedAttempts.outputs.failedEndpointId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/svix-resend-failed-attempt-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.