releases.shpreview

Developer API

Mon
Wed
Fri
JulAugSepOctNovDecJanFebMarAprMayJunJul
Less
More
Releases22Avg7/mo
  • Bill hold and release endpoints (beta) — Block or resume scheduled payments on a bill via POST /developer/v1/bills/{bill_id}/hold (with an optional reason) and POST /developer/v1/bills/{bill_id}/release. [View…
Read more →

The entity_type field on application creation now only accepts LLC as a valid value; previously accepted values like CORPORATION, PARTNERSHIP, and others are no longer accepted in requests, though existing applications with those values may still return them in responses. Added a new Fraud Omni investigation started audit log event type and an api channel enum value for the lead_referral_partner_channel field.

Read more →
  • New updated_at field on transactions — Transaction responses now include an updated_at timestamp representing the latest of user transaction time, settlement time, and interaction state update time. This makes it easier to understand exactly when a transaction was last…
Read more →
  • Original transaction ID for refunds — Transaction responses now include an original_transaction_id field that links refund transactions back to their original transaction. [View…
Read more →
  • New physical card endpoints (beta) — List, fetch, create, update, terminate, suspend, and unsuspend physical cards via dedicated endpoints under /developer/v1/cards/physical. These new endpoints use fund_id instead of the legacy spend_limit_id and return detailed…
Read more →
  • New all_requirements_met_and_approved field on transactions — Transaction responses now include an all_requirements_met_and_approved boolean indicating whether the transaction is fully approved and all cardholder requirements (receipts, memos, tracking categories) are…
Read more →
  • New fund_id field on transactions — Transaction responses now include a fund_id field that returns the unique identifier of the fund associated with the transaction. The existing limit_id field is deprecated and returns the same value as fund_id. [View…
Read more →
  • Purchase order owner assignment — You can now set the owner_id field when creating a purchase order to specify the owner, instead of defaulting to the API caller. [View…
Read more →
  • New treasury accounts endpoint (beta) — List all treasury accounts for your business, including wallet, brokerage, and managed portfolio accounts. Filter results with start and page_size pagination parameters. [View…
Read more →
  • Receipt OCR data now available — You can retrieve structured OCR data (currency code and line items with name, date, quantity, unit price, and total price) from receipts by passing the include_ocr_data query parameter on the List Receipts and Get Receipt endpoints. [View…
Read more →
  • New accounting codings endpoint (beta) — Post accounting coding selections to Ramp objects like transactions via POST /developer/v1/accounting/codings. Specify an object_id, object_type (currently TRANSACTION), and an array of accounting_coding_selections with…
Read more →
  • New audit log actor type — Added spend_request_agent as a new actor_type enum value for filtering and identifying Spend Request Agent activity in audit log events. [View…
Read more →
  • Bill payment date scheduling — You can now set an optional payment_date field when creating or updating bills via POST /developer/v1/bills and PATCH /developer/v1/bills/{bill_id} to schedule when a non-card payment should be initiated. Send null on update to…
Read more →
  • New audit log event types — Added several new event types for the audit logs endpoint: Cash manager recommendation reviewed, Forecast custom input deleted, Forecast custom input updated, Forecast settings updated, and Strict MFA setting updated. [View…
Read more →
  • New Comments endpoints (beta) — List and create comments on bills and spend requests via GET /developer/v1/comments/{object_type}/{object_id} and POST /developer/v1/comments/{object_type}/{object_id}. Supports bills and spend-requests as object_type values, with…
Read more →
  • Card expiration in Vault API responseGET /developer/v1/vault/cards/{card_id} now returns an expiration field with the card's expiration date in MMYY format, aligning the GET response with the existing POST response. [View…
Read more →
  • Purchase order memo updates — You can now update the memo field when patching a purchase order via PATCH /developer/v1/purchase-orders/{purchase_order_id}. [View…
Read more →
Last Checked
3h ago
Tracking since May 1, 2024