/
BI
bilflo
Search skmtc…
⌘K
Docs
Sign in
Docs
History
Schema
Generate
Filter operations
Clients
37
Companies
1
CompanySettings
10
CompanySignUp
3
Connect
5
ContractJobs
19
Contractors
15
CostCenters
5
CustomFields
4
Customizations
1
Dashboards
12
Diagnostics
9
DirectHires
6
EarningCodes
4
Employees
2
Entities
6
Erp2CompanyEvents
1
Erp2Lookups
9
Erp2PlacementDocuments
1
Erp2Webhook
1
Everee
1
Exports
3
post
/proliant/v1/exports/timecard
Exports one timecard now. Runs the identical handler the CAP topic and the Hangfire sweep use - there is one export code path, not three.
get
/proliant/v1/exports/pay-items/{companyIntegrationId}
Payroll-bound Bilflo pay items in use by this company - the left-hand side of the earning-code mapping screen. <br> Without this an administrator has to guess the pay item names, and real ones are company-specific ('Regular Time', '12-hr Duty Rate'), not the generic defaults the seed guesses. A guess that misses means the export fails on an unmapped pay item.
get
/proliant/v1/exports/history/{companyIntegrationId}
Export history: what was sent, what failed, and why. <br> The failure reason is the point. A history showing only "Failed" leaves an operator with no idea whether to map a pay item, reconnect the integration, or call Proliant. Pass status=Failed for the retry set.
FieldMappings
8
JobAdder
1
Layouts
3
Notifications
1
OAuth
4
OvertimeRules
1
PayBillItem
2
PayBillItemDetail
2
PayCodes
8
Placements
7
PrismHR
8
Processors
1
Query Engine
3
Reports
1
Subscriptions
2
Transactions
7
Users
18
Webhook
2
Workflows
32
Exports
Copy
Copy Markdown
Copy Markdown
Copying…
Copied
Copy failed
Changes to Exports one timecard now. Runs the identical handler the CAP topic and the Hangfire sweep use - there is one export code path, not three.
post
/proliant/v1/exports/timecard
Aug 12, 2026
1b4e8ebaeace
Revision changes
info
endpoint added