Ramp: Fetch a custom form collection response by ID — response body — custom form collection response custom form collection log entry allow comments, forms, label forms item fields item field mapping references item remote system
Fetch a custom form collection response by ID: response body, field custom_form_collection_response / custom_form_collection_log_entry / allow_comments, forms, label / forms / item / fields / item / field_mapping_references / item / remote_system. Complete fields and constraints for contract 2026-10-27.
API reference · Contract 2026-10-27
SDK schema: Fetch a custom form collection response by ID — response body — custom form collection response custom form collection log entry allow comments, forms, label forms item fields item field mapping references item remote system
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | string | Root | The type of remote/external system being integrated with. This enum identifies which third-party system the field mapping is for. Values are automatically registered by clients that implement FieldMappingFeature and register with FieldMappingClientRegistry. To add a new system: 1. Have your client implement FieldMappingFeature interface 2. Add the client to initialize_registries() in field_mapping/registry.py 3. Add the enum value here See suma/proxy/procurement_integrations/field_mapping_interface.py for details. Known values: ARAVO, DOCUSIGN, DRATA, IRONCLAD, LOGICGATE, MERGE, ONETRUST, VANTA |