SVB (Silicon Valley Bank)
Connect with SVB to manage banking operations and transactions.
Authentication
This connector uses Token-based authentication.
info
Set up your connection in the Abstra Console before using it in your workflows.
How to use
Using the Smart Chat
Execute the action "CHOOSE_ONE_ACTION_BELOW" from my connector "YOUR_CONNECTOR_NAME" using the params "PARAMS_HERE".
Using the Web Editor
from abstra.connectors import run_connection_action
result = run_connection_action(
connection_name="your_connection_name",
action_name="your_action_name",
params={
"param1": "value1",
"param2": "value2"
})
Available Actions
This connector provides 59 actions:
| Action | Purpose | Parameters |
|---|---|---|
| post_v1_security_oauth_token | Generate a JWE Token of client credential grant type | Content-Type (string) Accept (string) |
| post_v1_accounts_balances | This endpoint provides the balance information for an eligible entitled accounts | x-svb-request-id (string) data: { . account } (object) required |
| get_v1_accounts_details | This endpoint retrieves account details for a list of accounts. | x-svb-request-id (string) limit (integer) offset (integer) |
| post_v1_reporting_balances | Retrieve account balances for a list of accounts | x-svb-request-id (undefined) required data: { . account_number (array) . from_date (string) . to_date (string) . sort_params (array) . pagination_details } (object) required |
| post_v1_reporting_transactions | Retrieve account transactions for a list of accounts | x-svb-request-id (undefined) required data: { . account_number (array) . from_date (string) . to_date (string) . sort_params (array) . pagination_details } (object) required |
| post_v1_payment_account_transfers | Transfer funds between two accounts owned by the current customer | x-idempotency-key (undefined) x-jws-signature (undefined) required x-svb-request-id (undefined) data (undefined) required |
| get_v1_payment_account_transfers | List account transfers which have been sumitted by customer | limit (undefined) offset (undefined) x-svb-request-id (undefined) |
| get_v1_payment_account_transfers_by_id | Get account transfer by ID | id (undefined) x-svb-request-id (undefined) |
| get_v2_transfer_domestic_achs | Typically ACH transfers take 1-2 business days to complete. The status of an ACH transfer can take the following values: pending The initial status after creation. Pending ACH transfers are queued for processing and settlement. An ACH transfer can be canceled as long as it remains in the pending state. Depending on when the API request is made, a transfer may be pending for anywhere from a few minutes to a few hours. canceled The ACH transfer was canceled prior to being picked up for p | offset (integer) limit (integer) X-SVB-Correlation-ID (string) prefer (string) effective_entry_date (string) status (undefined) amount (integer) direction (string) identification_number (string) receiver_account_type (string) receiver_routing_number (string) settlement_priority (string) batch_id (string) sec_code (string) company_entry_description (string) fed_trace_number (string) mass_delivery_id (string) additional_information.key (string) additional_information.value (string) |
| post_v2_transfer_domestic_achs | Batch create domestic ACH transfers. Even single ach transfer can be created using this end point. The validation rules will be as follows : For any contract based validations , it will return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of batch details, still return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of particular transfers, that will | X-SVB-Correlation-ID (string) x-jws-signature (string) required x-idempotency-key (string) prefer (string) data: { . batch_details . transfers (array) } (object) required |
| get_v2_transfer_domestic_verified_achs | Typically ACH transfers take 1-2 business days to complete. The status of an ACH transfer can take the following values: pending The initial status after creation. Pending ACH transfers are queued for processing and settlement. An ACH transfer can be canceled as long as it remains in the pending state. Depending on when the API request is made, a transfer may be pending for anywhere from a few minutes to a few hours. canceled The ACH transfer was canceled prior to being picked up for p | offset (integer) limit (integer) X-SVB-Correlation-ID (string) prefer (string) effective_entry_date (string) status (undefined) amount (integer) direction (string) identification_number (string) settlement_priority (string) batch_id (string) sec_code (string) company_entry_description (string) fed_trace_number (string) provider_service (string) mass_delivery_id (string) additional_information.key (string) additional_information.value (string) provider_id (string) |
| post_v2_transfer_domestic_verified_achs | Batch create domestic ACH verified transfers. Even single ach transfer can be created using this end point. The validation rules will be as follows : For any contract based validations , it will return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of batch details, still return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of particular transfers, t | x-jws-signature (string) required X-SVB-Correlation-ID (string) x-idempotency-key (string) prefer (string) data: { . batch_details . transfers (array) } (object) required |
| get_v2_transfer_iat_domestic_achs | Typically ACH transfers take 1-2 business days to complete. The status of an ACH transfer can take the following values: pending The initial status after creation. Pending ACH transfers are queued for processing and settlement. An ACH transfer can be canceled as long as it remains in the pending state. Depending on when the API request is made, a transfer may be pending for anywhere from a few minutes to a few hours. canceled The ACH transfer was canceled prior to being picked up for p | offset (integer) limit (integer) X-SVB-Correlation-ID (string) prefer (string) effective_entry_date (string) status (undefined) amount (integer) direction (string) receiver_account_type (string) receiver_routing_number (string) settlement_priority (string) batch_id (string) sec_code (string) company_entry_description (string) fed_trace_number (string) mass_delivery_id (string) additional_information.key (string) additional_information.value (string) |
| post_v2_transfer_iat_domestic_achs | Batch create domestic international ACH transfers. Even single ach transfer can be created using this end point. The validation rules will be as follows : For any contract based validations , it will return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of batch details, still return 400 and will fail the entire request without persisting any data into DB. For any business validation failed because of particular transfe | x-jws-signature (string) required X-SVB-Correlation-ID (string) x-idempotency-key (string) prefer (string) data: { . batch_details . transfers (array) } (object) required |
| get_v2_transfer_domestic_achs_by_id | Retrieve a domestic ACH transfer based on ACH Id. | id (string) X-SVB-Correlation-ID (string) |
| patch_v2_transfer_domestic_achs_by_id | Update a Domestic ACH transfer ACH transfers may only be updated while their status remains pending. Any other status indicates that the ACH has been sent for processing and may no longer be modified. Note: PATCH operations can be performed only on non read only fields. | id (string) x-jws-signature (string) required X-SVB-Correlation-ID (string) data (array) required |
| get_v2_transfer_domestic_verified_achs_by_id | Retrieve a domestic ACH verified transfer based on ACH Id. | id (string) X-SVB-Correlation-ID (string) |
| patch_v2_transfer_domestic_verified_achs_by_id | Update a Domestic verified ACH transfer ACH transfers may only be updated while their status remains pending. Any other status indicates that the ACH has been sent for processing and may no longer be modified. Note: PATCH operations can be performed only on non read only fields. | id (string) x-jws-signature (string) required X-SVB-Correlation-ID (string) data (array) required |
| get_v2_transfer_iat_domestic_achs_by_id | Retrieve a domestic international ACH transfer based on ACH Id. | id (string) X-SVB-Correlation-ID (string) |
| patch_v2_transfer_iat_domestic_achs_by_id | Update a domestic international ACH transfer ACH transfers may only be updated while their status remains pending. Any other status indicates that the ACH has been sent for processing and may no longer be modified. Note: PATCH operations can be performed only on non read only fields. | id (string) x-jws-signature (string) required X-SVB-Correlation-ID (string) data (array) required |
| post_v2_transfer_reversal | ACH Reversals can be initiated to recover transactions, previously originated in API Banking by error, for specific reasons such as Duplicate Entry, Incorrect Receiver, Incorrect Dollar Amount, Debits sent earlier than intended, Credits sent later than intended and PPD Credit related to termination/separation from employment. | X-SVB-Correlation-ID (string) x-jws-signature (string) required x-idempotency-key (string) prefer (string) data: { . batch_details . reversal_details_single_mass_id . reversal_details_multiple_id (array) } (object) required |
| patch_v2_transfer_reversal_by_id | ACH Reversal may be updated while their status remains Pending. Any other status indicates that the ACH Reversal has been sent for processing and may no longer be modified. Note: PATCH operations can be performed only on reason for reversal and settlement priority. | id (string) x-jws-signature (string) required X-SVB-Correlation-ID (string) data: { . reason_for_reversal (string) . settlement_priority (string) } (object) required |
| post_v1_payment_global_achs | Create a Global Ach Payment Request | x-idempotency-key (undefined) required x-jws-signature (string) required x-svb-request-id (undefined) data: { . debtor_account . requested_execution_date . payment_type . amount . end_to_end_id . ultimate_debtor_details . creditor_details . creditor_agent . payment_details } (object) required |
| get_v1_payment_global_achs | Retrieve Global ACH Payment requests placed by a client . | x-svb-request-id (undefined) offset (integer) limit (integer) status (string) requested_execution_date_from (string) requested_execution_date_to (string) |
| get_v1_payment_global_achs_by_id | Retrieve Global ach payment based on Id. | id (undefined) x-svb-request-id (undefined) |
| delete_v1_payment_global_achs_by_id | Delete a scheduled Global Ach Payment based on Id. | id (undefined) x-svb-request-id (undefined) |
| post_v1_payment_instant_payments | Create an Instant Payment Request | x-idempotency-key (undefined) required x-jws-signature (string) required x-svb-request-id (undefined) data (array) required |
| get_v1_payment_instant_payments | Retrieve Instant Payment requests placed by a client . | x-svb-request-id (undefined) offset (integer) limit (integer) status (string) requested_execution_date_from (string) requested_execution_date_to (string) |
| get_v1_payment_instant_payments_by_id | Retrieve Instant Payment request based on Id. | id (undefined) x-svb-request-id (undefined) |
| post_v2_payment_wires | Create a Wires Payment Request | x-idempotency-key (undefined) required x-jws-signature (string) required x-svb-request-id (undefined) data: { . debtor_account . requested_execution_date . payment_type . amount . payment_identification . ultimate_debtor_details . creditor_details . creditor_agent . intermediary_agent . payment_details } (object) required |
| get_v2_payment_wires | Retrieve Wire Payment requests placed by a client . | x-svb-request-id (undefined) offset (integer) limit (integer) status (string) requested_execution_date_from (string) requested_execution_date_to (string) |
| get_v2_payment_wires_by_id | Retrieve wires payment based on Id. | id (undefined) x-svb-request-id (undefined) |
| delete_v2_payment_wires_by_id | Delete a scheduled Wire Payment. | id (undefined) x-svb-request-id (undefined) |
| post_v1_payment_stop_checks | Stop Check requests will prevent payment of issued checks until the expiration date of the Stop Check request | x-svb-request-id (string) x-jws-signature (string) required data (array) required |
| get_v1_payment_stop_checks | List all stop check requests submitted by Client. | offset (integer) limit (integer) x-svb-request-id (string) check_number (string) expiration_date_before (string) status (string) status_detail (string) reason (undefined) recipient (undefined) amount (undefined) |
| get_v1_payment_stop_checks_by_id | Retrieve a Stop Check request based on Id. | id (string) x-svb-request-id (string) |
| get_v2_card_virtualcards | Retrieves a list of virtual cards you've previously created in creation order. This call returns a single page of data. Paging is available for this endpoint Filtering is available for this endpoint The results can be filtered by matching fields in the metadata portion of the virtual card. To filter, use the the metadata.key=value parameter. The metadata portion is a required literal string, key is the name of the sub field in metadata, and value is the string to match. For | metadatakey (string) metadatavalue (string) purchase_request_id (string) offset (integer) limit (integer) Prefer (string) |
| post_v2_card_virtualcards | Important: There is a distinction between the mastercard_data and metadata fields: metadata is a map of client-provided string data that enables clients to fetch and filter virtual cards based additional fields. These fields are never sent to MasterCard, but they exist to ease integration with the SVB API. This field can contain up to 8000 characters. mastercard_data fields are sent to MasterCard as “Custom Data Fields”, and they must be defined as part of the VCN template in the SmartData | X-SVB-Correlation-ID (string) x-jws-signature (string) required x-idempotency-key (string) data (undefined) required |
| get_v2_card_virtualcards_by_id | Retrieves a virtual card that has been previously created. Use the unique ID returned from the previous request to identify which virtual cards to retrieve. Note the following: card_number is only included in the response with header PREFER=RETURN_REPRESENTATION Links to the fiterable, pagable realtime clearings and authorizations indexes are returned with the vcn record. | id (string) Prefer (string) |
| delete_v2_card_virtualcards_by_id | Canceling a virtual card prevents that card from being used for future purchases with a merchant. Canceling a virtual card does not stop any in-progress transactions in which a merchant has an authorization from clearing and settling. A canceled VCN will also continue to accept return/refund transactions. This endpoint doesn’t return a body, but instead returns a HTTP Status Code 204 No Content. | id (string) |
| patch_v2_card_virtualcards_by_id | Updates a virtual card that has been previously created and returns the updated Virtual Card. Use the unique ID returned from the previous request to identify which virtual cards to update. Takes the same parameters as the Create endpoint. All fields are optional when updating a virtual card. For values that are not passed, the original virtual card value will be preserved. | id (string) X-SVB-Correlation-ID (string) x-jws-signature (string) required Prefer (string) data (array) required |
| get_v2_card_virtualcard_authorizations | Retrieves a list of authorization events in creation order. This call returns a single page of data. Paging is available for this endpoint Filtering is available for this endpoint with the fieldname params as described in the query parameters section. | billing_value (string) purchase_request_id (string) issuer_response (string) vcn_response (string) mcc (string) card_holder_transaction_type_code (string) merchant_id (string) transaction_date_time_before (string) transaction_date_time_after (string) billing_currency_code (string) mcc_description (string) merchant_value (string) merchant_name (string) approval_code (string) vcn_uuid (string) offset (integer) limit (integer) |
| get_v2_card_virtualcard_clearings | Retrieves a list of clearing events in creation order. This call returns a single page of data. Paging is available for this endpoint Filtering is available for this endpoint with the fieldname params as described in the query parameters section. | acquirer_ica (string) approval_code (string) purchase_request_id (string) authorization_date_before (string) authorization_date_after (string) billing_value (string) clearing_type (string) exchange_rate (string) mcc (string) mcc_description (string) merchant_value (string) merchant_currency_code (string) merchant_id (string) merchant_name (string) settlement_date_before (string) settlement_date_after (string) billing_currency_code (string) offset (integer) limit (integer) vcn_uuid (string) |
| get_v2_card_virtualcard_real_cards | Every virtual card maps to a single real credit card i.e. a traditional plastic credit card. Your account may have one or more real credit cards associated with it. If only one card is configured, new virtual cards will map by default to that single card. If multiple real cards are configured, it is best to specify the rcn_id and rcn_alias of one of the objects returned via this endpoint when creating a new virtual card. | No parameters |
| get_v2_card_virtualcard_suppliers | this description is being updated by business, please wait | No parameters |
| get_v2_card_virtualcard_templates | this description is being updated by business, please wait | No parameters |
| get_v2_card_virtualcard_templates_by_id | this description is being updated by business, please wait | id (string) |
| get_v2_event_event_types | Call this endpoint to receive a list of event types. | offset (integer) limit (integer) x-svb-request-id (string) |
| get_v2_event_event_types_by_event_type_id | Call this endpoint to retrieve a particular event type by id. | event_type_id (string) x-svb-request-id (string) |
| get_v2_event_events_by_event_id | Call this endpoint to retrieve an event. | event_id (string) x-svb-request-id (string) |
| get_v2_event_events | Call this endpoint to get a list of all events | offset (integer) limit (integer) x-svb-request-id (string) |
| get_v2_event_publishers_by_publisher_id | Call this endpoint to retrieve a publisher. | publisher_id (string) x-svb-request-id (string) |
| get_v2_event_publishers | Call this endpoint to get a list of all publishers | offset (integer) limit (integer) x-svb-request-id (string) |
| post_v2_event_subscriptions | Call this endpoint to create a new subscription. When an event is triggered, then the callback URL will receive a POST of the event if there is an active subscription for that event type. Callback urls must be unique. | x-svb-request-id (string) x-jws-signature (string) required data: { . event_type_names (array) . client_secret_key (string) . status (string) . callback_url (string) } (object) required |
| get_v2_event_subscriptions | Call this endpoint to get a list of all created subscriptions. | offset (integer) limit (integer) x-svb-request-id (string) |
| get_v2_event_subscriptions_by_subscription_id | Call this endpoint to retrieve a specific subscription by its id. | subscription_id (string) x-svb-request-id (string) |
| patch_v2_event_subscriptions_by_subscription_id | Call this endpoint to update a subscription. Fields that are read-only can not be updated. | subscription_id (string) x-svb-request-id (string) data (array) required |
| get_v2_event_subscriptions_by_subscription_id_test | Call this endpoint to manually trigger a subscription for testing purposes. Both active and inactive subscriptions can be tested this way. The event type of the event send will be 0 to indicate testing data. | subscription_id (string) x-svb-request-id (string) |
| get_v1_reference_reachability_instant_payments_by_creditor_agent_id | Retrieves confirmation that a specified creditor agent is a participant of payment networks | creditor_agent_id (string) x-svb-request-id (undefined) |