Your data, in your spreadsheet or your own tool
The main lists export to Excel and CSV. Your own work exports to Excel and CSV almost everywhere you made it, and most of it prints. Capture and Enterprise members get an API key that reads the same lists the app shows, for companies that want the data inside their own systems. Enterprise comes with an API onboarding call.
Excel and CSV export of the record
Twenty-eight lists export as Excel or CSV with the filters and the order you set, up to your plan's monthly rows and 20,000 rows a file: open notices, award history, recompetes, companies, SAM registrants, subawards, grant awards, rules, bills, the forecast, price history, vehicles, labor rates, contacts, grant opportunities, exclusions, the defense budget, sole source notices, buying offices, companies about to graduate, who to team with, the way in, clauses, and the agency, NAICS, PSC, set-aside and region directories. Columns are the fields you see in the app plus identifiers like the USASpending award ID and the SAM.gov notice ID, so you can join back to the source. Cells that start with a formula character are escaped so a spreadsheet never runs them.
List export is on paid plans. On One Code your own work still leaves as a file: the readiness checklist, your company record and a pursuit brief. A file of your own work is never counted against the monthly rows.
Your own work, as a file
| What | Excel and CSV | |
|---|---|---|
| A bid worksheet | Yes | Yes |
| A contract | Yes | Yes |
| An invoice | Yes | Yes |
| The record of changes to a contract's costs | Yes | No |
| The pipeline, or one pursuit | Yes | Yes |
| Your open tasks | Yes | No |
| The calendar, for the month on screen | Yes | Yes |
| Wins and losses | Yes | Yes |
| A plan for a target in Customer intelligence | Yes | Yes |
| A timesheet | Yes | Yes |
| The labor distribution for a period | Yes | No |
| The staff list | Yes | Yes |
| Pay runs for a fiscal year | Yes | No |
| A rate set | Yes | Yes |
| The cost ledger | Yes | Yes |
Your own work is never counted against the monthly rows. The buttons are on the screen the work is on.
The API, on Capture and Enterprise
On Capture and Enterprise, one key reads the record from your own tools: the same lists the app shows, with the same filters, answered as JSON.
It covers notices, awards, companies, buying offices and agencies, contracting people, vehicles, subawards and grants, small business research (SBIR and STTR), forecast, price bands, ways in, rules, bills and clauses, defense budget, codes, states, labor rates and wages, per diem rates, court and lobbying, cloud services (FedRAMP), your own work and exports. Any list also leaves through the API as a CSV or Excel file.
A key reads and changes nothing. It is shown once when you make it, and you can replace it from Users and billing at any time.
The API reference lists every route with its parameters, its fields and an example.
Where it stops
The API is read only: a key reads, and anything that would add, change or remove something is refused. A key that asks too often is told to wait and how long. Bulk redistribution of the compiled database is not allowed under the acceptable use policy; your own company's systems are exactly what it is for.
Related
- API referenceEvery route a key can call, with its parameters, fields and an example.
- PricingExport rows and API access by plan.
- Acceptable useWhat you may do with exported data.
See who was last awarded in your NAICS
Every code, every buying office, every vendor and every recompete, organized from the federal record and read nightly. Start on one code with no card. A plan opens every code.
Try the live demo The real app on one code. No email needed.