Automate PocketSmith

What PocketSmith is

The PocketSmith API

API host: api.pocketsmith.com

What HumDay can do in PocketSmith

25 documented operations change something in PocketSmith.

• POSTCreate an account in user/users/{id}/accounts
• PUTUpdate the display order of accounts in user/users/{id}/accounts
• POSTCreate event in scenario/scenarios/{id}/events
• POSTCreate category in user/users/{id}/categories
• POSTCreate attachment in user/users/{id}/attachments
• POSTCreate institution in user/users/{id}/institutions
• PUTUpdate user/users/{id}
• DELETEDelete event/events/{id}
• PUTUpdate event/events/{id}
• DELETEDelete forecast cache for user/users/{id}/forecast_cache
• POSTCreate category rule in category/categories/{id}/category_rules
• POSTCreate a transaction in transaction account/transaction_accounts/{id}/transactions
• DELETEDelete account/accounts/{id}
• PUTUpdate account/accounts/{id}
• DELETEDelete category/categories/{id}
• PUTUpdate category/categories/{id}
• DELETEDelete attachment/attachments/{id}
• PUTUpdate attachment/attachments/{id}
• DELETEDelete institution/institutions/{id}
• PUTUpdate institution/institutions/{id}
• DELETEDelete transaction/transactions/{id}
• PUTUpdate a transaction/transactions/{id}
• PUTUpdate transaction account/transaction_accounts/{id}
• POSTAssigns attachment to transaction/transactions/{id}/attachments
• DELETEUnassigns attachment in transaction/transactions/{transaction_id}/attachments/{attachment_id}

What HumDay can read from PocketSmith

These are the operations a schedule or a trigger can watch.

• GETList events in user./users/{id}/events
• GETGet the authorised user/me
• GETList budget for user/users/{id}/budget
• GETList labels in user/users/{id}/labels
• GETList accounts in user/users/{id}/accounts
• GETList categories in user/users/{id}/categories
• GETList institutions in user/users/{id}/institutions
• GETList transactions in user/users/{id}/transactions
• GETList category rules in user/users/{id}/category_rules
• GETList saved searches in user/users/{id}/saved_searches
• GETList transaction accounts in user/users/{id}/transaction_accounts
• GETGet user/users/{id}
• GETGet event/events/{id}
• GETList currencies/currencies
• GETList time zones/time_zones
• GETList events in scenario./scenarios/{id}/events
• GETLists attachments in user/users/{id}/attachments
• GETGet budget summary for user/users/{id}/budget_summary
• GETGet trend analysis for user/users/{id}/trend_analysis
• GETList transactions in account/accounts/{id}/transactions
• GETList accounts in institution/institutions/{id}/accounts
• GETList transactions in categories/categories/{id}/transactions
• GETList attachments in transaction/transactions/{id}/attachments
• GETList transactions in transaction account/transaction_accounts/{id}/transactions
• GETGet account/accounts/{id}
• GETGet category/categories/{id}
• GETGet currency/currencies/{id}
• GETGet attachment/attachments/{id}
• GETGet institution/institutions/{id}
• GETGet a transaction/transactions/{id}
• GETGet transaction account/transaction_accounts/{id}

How automating PocketSmith works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live PocketSmith account.
4. Grant access, then go live. You approve the specific PocketSmith operations it may use — and only those.

Automate PocketSmith with these

• Stripe442 operations
• Zuora Reference Billing428 operations
• bunq421 operations
• PayRun.IO389 operations
• Sinao272 operations
• Xero Accounting224 operations
• The Plaid191 operations
• Biapi Budgea Documentation167 operations
• Naviplancentral Advicent.FactFinderService151 operations
• Bigredcloud Big Red Cloud111 operations
• Codat Accounting105 operations
• Portfoliooptimizer Portfolio Optimizer83 operations

Categories

• Finance

Questions about PocketSmith automation

Can HumDay connect to PocketSmith?

Yes. HumDay reads PocketSmith's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 56 operations are documented.

Do I need to write code to automate PocketSmith?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your PocketSmith account.

What can HumDay do in PocketSmith?

25 of the 56 documented operations change something in PocketSmith, and 31 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my PocketSmith account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to PocketSmith is held behind that approval.

Where this came from

The operations above are read from a published API description for PocketSmith at raw.githubusercontent.com/pocketsmith/api/master/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.