Apideck java
Skill apideck-libraries/api-skills/providers/cursor/plugin/skills/apideck-java
One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.
npx -y skills add apideck-libraries/api-skills --skill apideck-javaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Apideck Unified API integration patterns for Java. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using Java. Covers the com.apideck:unify Maven package, authentication, CRUD operations, pagination, async support, and Vault connection management.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.9 KB, as published. Nobody here has run it
Apideck Java SDK Skill
Overview
The Apideck Unified API provides a single integration layer to connect with 200+ third-party services across accounting, CRM, HRIS, file storage, ATS, e-commerce, and more. The official Java SDK (com.apideck:unify) provides typed clients for all unified APIs.
Installation
Gradle:
implementation 'com.apideck:unify:0.30.3'
Maven:
<dependency>
<groupId>com.apideck</groupId>
<artifactId>unify</artifactId>
<version>0.30.3</version>
</dependency>
Requires JDK 11 or later.
IMPORTANT RULES
- ALWAYS use the
com.apideck:unifySDK. DO NOT make raw HTTP calls to the Apideck API. - ALWAYS pass
apiKey,appId, andconsumerIdwhen building the client. - USE
serviceIdon requests to specify which downstream connector to use. - USE the fluent builder pattern for constructing requests.
- ALWAYS handle errors with try/catch using
ApideckErroras the base class. - DO NOT store API keys in source code. Use environment variables.
Quick Start
import com.apideck.unify.Apideck;
import com.apideck.unify.models.operations.*;
Apideck sdk = Apideck.builder()
.consumerId("your-consumer-id")
.appId("your-app-id")
.apiKey(System.getenv("APIDECK_API_KEY"))
.build();
sdk.crm().contacts().list()
.serviceId("salesforce")
.limit(20)
.callAsStream()
.forEach(page -> {
page.getContactsResponse().ifPresent(res ->
res.getData().forEach(contact ->
System.out.println(contact.getName())
)
);
});
SDK Patterns
Client Setup
import com.apideck.unify.Apideck;
Apideck sdk = Apideck.builder()
.consumerId("your-consumer-id")
.appId("your-app-id")
.apiKey(System.getenv("APIDECK_API_KEY"))
.build();
Async client:
import com.apideck.unify.AsyncApideck;
AsyncApideck asyncSdk = Apideck.builder()
.consumerId("your-consumer-id")
.appId("your-app-id")
.apiKey(System.getenv("APIDECK_API_KEY"))
.build()
.async();
CRUD Operations
Uses a fluent builder pattern: sdk.{category}().{resource}().{operation}().
import com.apideck.unify.models.components.*;
import com.apideck.unify.models.operations.*;
// LIST
sdk.crm().contacts().list()
.serviceId("salesforce")
.limit(20)
.filter(ContactsFilter.builder().email("[email protected]").build())
.sort(ContactsSort.builder()
.by(ContactsSortBy.UPDATED_AT)
.direction(SortDirection.DESC)
.build())
.call();
// CREATE
sdk.crm().contacts().create()
.serviceId("salesforce")
.contact(ContactInput.builder()
.firstName("John")
.lastName("Doe")
.emails(List.of(Email.builder()
.email("[email protected]")
.type(EmailType.PRIMARY)
.build()))
.phoneNumbers(List.of(PhoneNumber.builder()
.number("+1234567890")
.type(PhoneNumberType.MOBILE)
.build()))
.build())
.call();
// GET
sdk.crm().contacts().get()
.id("contact_123")
.serviceId("salesforce")
.call();
// UPDATE
sdk.crm().contacts().update()
.id("contact_123")
.serviceId("salesforce")
.contact(ContactInput.builder().firstName("Jane").build())
.call();
// DELETE
sdk.crm().contacts().delete()
.id("contact_123")
.serviceId("salesforce")
.call();
Pagination
Multiple approaches available:
// Stream (recommended)
sdk.accounting().invoices().list()
.serviceId("quickbooks")
.limit(50)
.callAsStream()
.forEach(page -> {
// handle page
});
// Iterable
for (var page : sdk.accounting().invoices().list()
.serviceId("quickbooks")
.limit(50)
.callAsIterable()) {
// handle page
}
// Reactive Streams (for Project Reactor, RxJava, etc.)
var publisher = sdk.accounting().invoices().list()
.serviceId("quickbooks")
.limit(50)
.callAsPublisher();
Async Support
Returns CompletableFuture<T> for standard operations:
AsyncApideck asyncSdk = sdk.async();
asyncSdk.crm().contacts().list()
.serviceId("salesforce")
.limit(20)
.call()
.thenAccept(res -> {
// handle response
});
Error Handling
import com.apideck.unify.models.errors.*;
try {
sdk.crm().contacts().get()
.id("invalid")
.serviceId("salesforce")
.call();
} catch (BadRequestResponse e) {
System.err.println("Bad request: " + e.message());
} catch (UnauthorizedResponse e) {
System.err.println("Invalid API key");
} catch (NotFoundResponse e) {
System.err.println("Record not found");
} catch (PaymentRequiredResponse e) {
System.err.println("API limit reached");
} catch (UnprocessableResponse e) {
System.err.println("Validation error: " + e.message());
} catch (ApideckError e) {
System.err.println("API error " + e.code() + ": " + e.message());
}
Retry Configuration
import com.apideck.unify.utils.BackoffStrategy;
import com.apideck.unify.utils.RetryConfig;
import java.util.concurrent.TimeUnit;
Apideck sdk = Apideck.builder()
.retryConfig(RetryConfig.builder()
.backoff(BackoffStrategy.builder()
.initialInterval(1L, TimeUnit.MILLISECONDS)
.maxInterval(50L, TimeUnit.MILLISECONDS)
.maxElapsedTime(1000L, TimeUnit.MILLISECONDS)
.baseFactor(1.1)
.jitterFactor(0.15)
.retryConnectError(false)
.build())
.build())
.consumerId("your-consumer-id")
.appId("your-app-id")
.apiKey(System.getenv("APIDECK_API_KEY"))
.build();
API Namespaces
| Namespace | Resources |
|---|---|
sdk.accounting().* | invoices, bills, payments, customers, suppliers, ledgerAccounts, journalEntries, taxRates, creditNotes, purchaseOrders, balanceSheet, profitAndLoss, and more |
sdk.crm().* | contacts, companies, leads, opportunities, activities, notes, pipelines, users |
sdk.hris().* | employees, companies, departments, payrolls, timeOffRequests |
sdk.fileStorage().* | files, folders, drives, driveGroups, sharedLinks, uploadSessions |
sdk.ats().* | applicants, applications, jobs |
sdk.vault().* | connections, consumers, sessions, customMappings, logs |
sdk.webhook().* | webhooks, eventLogs |
Gives 0 of the 12 instructions most sales crm skills give
Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06
- Read product marketing context before writing if it existsin 22 of 361, across 14 files
- keep the ask low-frictionin 16 of 361, across 7 files
- Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
- personalize every outbound messagein 13 of 361, across 4 files
- confirm connection status is activein 13 of 361, across 4 files
- Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
- State if personalization context is missingin 13 of 361, across 4 files
- Cut any sentence that does not drive a replyin 13 of 361, across 4 files
- Use proof instead of adjectivesin 12 of 361, across 3 files
- Use a single, low-friction call to actionin 12 of 361, across 4 files
- Calibrate tone to the specific audiencein 12 of 361, across 3 files
- Make each follow-up email add new valuein 12 of 361, across 6 files
Said here and by no other author read
- Use the official SDK package
- Pass apiKey, appId, and consumerId
- Use ServiceId to specify the connector
- handle errors with try catch using api exception base
- use environment variables for api keys
- use the fluent builder pattern for requests
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.