API Reference

Correct a form on a manual filing

post
https://api.wingspan.app/v3/compliance/tax-filings//correct

Issues a caller-driven correction against a form produced by this filing. This is the manual escape hatch: it is allowed only after the filing has been switched to manual management (managementMode: Manual) and returns 409 Conflict while the filing is still Managed — managed corrections go through the data-driven adjust action instead. Depending on the strategy it creates a corrected form, a voiding submission, or a voiding submission plus a replacement form, and the returned data lists every form created by the command.
Available in 1099 phase 2

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Unique identifier of the tax filing

Body Params

Issues a correction against a form produced by this filing.

string
required

The form to correct.

string
enum

Omitted means Correction. Correction creates one corrected form. Void records a voiding submission. VoidAndRefile records a voiding submission and creates a replacement form.

Allowed:
string
enum
Allowed:
string

State code when jurisdiction is State (for example, CA).

formData

Type-specific form data. The nested type discriminator must match the parent Form.type, which remains the canonical form kind for filtering and lifecycle decisions. The full schema for each type is published by the FormSchema registry.

recipient
object

A party named on the form (recipient or issuer).

string

Reason for the correction.

metadata
object

Free-form key-value pairs. Max 50 keys; key length at most 40 characters; value length at most 500 characters. Where a list endpoint declares metadata filtering, it uses the QueryQL namespace via filter[metadata.{key}][eq]=value or filter[metadata.{key}][in][]=value. Endpoints that do not declare the dynamic Metadata filter do not support Metadata filtering.

Headers
string
length between 1 and 255
^[\x21-\x7e]{1,255}$

Optional idempotency token for authenticated POST and PATCH requests. Reusing the same key and body returns the cached response for 24 hours, except credential operations that explicitly document a 409 because one-time secret material is never cached; reusing it with a different body returns 409 IdempotencyKeyConflict. Use 1-255 printable ASCII characters.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Updated 4 months ago

Did this page help you?
Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json

Updated 4 months ago

Did this page help you?