Create a Form 1099

The following is an example of creating a Form 1099. Note that all form types follow the same pattern for creation, but for more information on a specific form type, please read the full reference:


Generating a Form 1099

To create a Form 1099 directly from our API you’ll need information about the Payee, information about the Payer, and specific form fields values for your that form type.

tin or tinFingerprint?

For both the Payer and Payee we allow you to pass either the plain text tin or a previously created tinFingerprint.

cURL
1curl \
2  -request POST \
3  -url https://sandbox-api.withabound.com/v4/documents/1099-K \
4  -header 'accept: application/json' \
5  -header 'content-type: application/json' \
6  --data '{
7  "filingYear": 2023,
8  "payer": {
9    "name": "Hooli",
10    "tin": "111111111",
11    "address": "1401 N Shoreline Blvd",
12    "address2": "Suite 1",
13    "city": "Mountain View",
14    "state": "CA",
15    "postalCode": "94043",
16    "country": "US",
17    "phoneNumber": "6501014096"
18  },
19  "payee": {
20    "name": "Ada Lovelace",
21    "tin": 000000000",
22    "address": "256 Byron Street",
23    "address2": "Suite 32",
24    "city": "Palo Alto",
25    "state": "CA",
26    "postalCode": "94306",
27    "country": "US"
28  },
29  "formFields": {
30    ...
31  }
32}'

Response

The response will contain all the information from the request, plus the following additional information:

  • a unique documentId
  • the createdAt timestamp
  • thepayerUrl that links to the generated pdf of the Payer’s copy of the form
  • the payeeUrl that links to the generated pdf of the Payee’s copy of the form
  • the status of the form
JSON
1{
2  "id": "documentId_sampletTtqNfulW8",
3  "createdAt": "2023-01-01T00:00:00.000Z",
4  "status": "CREATED",
5  "payerUrl": "https://tax-documents-sandbox.s3.us-west-2.amazonaws.com/documents/FORM-1099-COPY-C.pdf",
6  "payeeUrl": "https://tax-documents-sandbox.s3.us-west-2.amazonaws.com/documents/FORM-1099-COPY-B.pdf",
7  "filingYear": 2022,
8  "payer": {
9    "name": "Hooli",
10    "tin": "*******11",
11    "address": "1401 N Shoreline Blvd",
12    "address2": "Suite 1",
13    "city": "Mountain View",
14    "state": "CA",
15    "postalCode": "94043",
16    "country": "US",
17    "phoneNumber": "6501014096",
18    "tinType": "BUSINESS",
19    "tinFingerprint": "tinFingerprint_sample847jI1LwxF",
20    "tinVerificationId": "tinVerificationId_sample1b0E6efa89",
21    "tinVerificationStatus": "MATCH",
22  },
23  "payee": {
24    "name": "Ada Lovelace",
25    "tin": "*******00",
26    "address": "256 Byron Street",
27    "address2": "Suite 32",
28    "city": "Palo Alto",
29    "state": "CA",
30    "postalCode": "94306",
31    "country": "US",
32    "tinType": "INDIVIDUAL",
33    "tinFingerprint": "tinFingerprint_samplehy2BWO6JJG",
34    "tinVerificationId": "tinVerificationId_sample41SD71AV8f",
35    "tinVerificationStatus": "MATCH",
36  },
37  "formFields": {
38    ...
39  }
40}

Automatic Tin Verification

It’s important to note that if the combination of the Payee’s or Payer’s name and tin has not been seen before on the Abound platform, a Tin Verification will automatically be created. In the event that a new Tin Verification was created, a tinVerificationId will be returned in the response nested in the payee and/or the payer object(s).