Ramp: Create a new custom accounting field
Ramp accounting.postCustomFieldListResource: arguments, response, policy and SDK examples.
← Accounting operations · Get started
Operation ramp.post_custom_field_list_resource
Provider route: POST /developer/v1/accounting/fields. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/ramp with npm, or alter-sdk-ramp with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { RampIntegration } from "@alter-ai/ramp";
async function execute(input: Parameters<RampIntegration["accounting"]["postCustomFieldListResource"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new RampIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.accounting.postCustomFieldListResource(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_ramp import RampIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = RampIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.accounting.post_custom_field_list_resource(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
body | Model | Required within parent | Expand Create a Ramp-only accounting field — request body — body |
Referenced models: Create a Ramp-only accounting field — request body — body
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Fetch a custom accounting field — response body |
Referenced models: Fetch a custom accounting field — response body
Schemas
Section titled “Schemas”Create a Ramp-only accounting field — request body — body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
accounting_connection_id | JSON | Optional | |
accounting_connection_id (anyOf 1) | string | Alternative | Specify an accounting connection. This connection must be an accounting API based connection. If not provided we default to the current active connection. Format: uuid |
accounting_connection_id (anyOf 2) | null | Alternative | |
display_name | JSON | Optional | |
display_name (anyOf 1) | string | Alternative | The name of the custom accounting field as shown on Ramp. |
display_name (anyOf 2) | null | Alternative | |
id | string | Required within parent | Remote/external ID of custom accounting field from ERP system. |
input_type | string | Required within parent | The input type for the custom accounting field. One of: BOOLEAN, FREE_FORM_TEXT, SINGLE_CHOICE |
is_required_for | array | Optional | Types of objects that require this accounting field to be used for coding before they can be marked as ready to sync. |
is_required_for[] | string | Each item | One of: BILL, BILL_PAYMENT, CUSTOMER, INVOICE, PURCHASE_ORDER, REIMBURSEMENT, SPEND_PROGRAM, TRANSACTION, TRANSFER_LEDGER_ENTRY_MAPPING, VENDOR_CREDIT |
is_splittable | boolean | Optional | If set to True, the accounting field can be used to annotate split line items. If not specified, the default value will be False. |
name | string | Required within parent | name of the custom accounting field. |
Fetch a custom accounting field — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
accounting_connection_id | string | Required within parent | ID of the accounting connection that the custom accounting fields are uploaded to. Format: uuid |
created_at | string | Optional | Format: date-time |
display_name | JSON | Required within parent | |
display_name (anyOf 1) | string | Alternative | Name of the custom accounting field on Ramp. |
display_name (anyOf 2) | null | Alternative | |
id | string | Optional | Remote/external ID of custom accounting field from ERP system. |
input_type | string | Required within parent | The input type for the custom accounting field. Known values: BOOLEAN, DATE, FREE_FORM_TEXT, SINGLE_CHOICE |
is_active | boolean | Optional | |
is_required_for | array | Required within parent | Types of objects that require this accounting field to be used for coding before they can be marked as ready to sync. Read only: true |
is_required_for[] | string | Each item | Known values: BILL, BILL_PAYMENT, CUSTOMER, INVOICE, PURCHASE_ORDER, REIMBURSEMENT, SPEND_PROGRAM, TRANSACTION, TRANSFER_LEDGER_ENTRY_MAPPING, VENDOR_CREDIT |
is_splittable | boolean | Optional | |
name | string | Optional | Name of the custom accounting field in the remote ERP system. |
provider_name | JSON | Required within parent | |
provider_name (anyOf 1) | string | Alternative | Name of the accounting connection that the custom accounting field is uploaded to. Read only: true |
provider_name (anyOf 2) | null | Alternative | |
ramp_id | string | Optional | id to uniquely identify a custom accounting field within Ramp system Format: uuid |
updated_at | string | Optional | Format: date-time |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: ramp.post_custom_field_list_resource. Catalog operation: post_custom_field_list_resource. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["accounting:write"]