BluebulbAPI
    API reference/Payments received
    POST

    Resend a payment webhook

    Rolling out
    POST{baseUrl}/api/payins/{id}/resend-webhook

    Sends the funding webhook for a payment again — for example, if your endpoint was down.

    This endpoint is part of an API release that is still rolling out. Fields and endpoints marked Rolling out may not be available on your account yet.

    Authentication

    Send your API key and a request signature on every call. Requests must also come from an IP address on your allowlist — see Authentication.

    Headers

    x-api-key
    required
    string
    Your API key, <appId>.<secret>. See Authentication.
    X-Signature
    required
    string
    Base64 RSA-SHA256 signature of the request. See Request signing.
    X-Signature-Timestamp
    required
    string
    Unix time in milliseconds used in the signature. Must be within 5 minutes of Orbita's clock.
    Content-Type
    required
    string
    application/json, or multipart/form-data when the endpoint accepts a file.

    Path parameters

    id
    required
    string (uuid)
    The payment ID.

    Behaviour

    Re-sends exactly the same payload as the latest webhook for this payment, as a new delivery. Nothing about the payment or your balance changes, however many times you call it. No request body.

    Response

    data identifies the new delivery. Every response is wrapped in the standard envelope.

    id
    string (uuid)
    ID of the new webhook delivery.

    Errors

    Errors specific to this endpoint:

    404
    Payment record not found
    No payment with this ID belongs to your business.
    404
    No webhook delivery found for this payment
    No webhook was ever sent for this payment — for example, because no webhook URL was set up when it arrived.

    Plus the errors every endpoint can return — authentication, signing, rate limiting and server errors. See Responses & errors.