https://docs.cdp.coinbase.com/llms.txt
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 15/100
- Issue-Typ
- Dokumentation
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- java
- Bereich
- documentation
Rechercherichtung
Start by inspecting the repository’s documentation and comparing its content with the linked Coinbase Prime docs. The issue does not identify a specific file or requested change, and its body largely reproduces documentation with unrelated links. Clarify what needs changing before implementation; done criteria are not specified.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
https://base.app/invite/oxsarawuts2702/single/coinbase.com/118792c3-0fb5-4ce6-b243-d3c3e4f7f1b0
Documentation Index
Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt
Use this file to discover all available pages before exploring further.
Account Structure
Entities and Portfolios
Coinbase Prime uses a hierarchical account structure with three levels: organizations, entities, and portfolios. This structure supports both simple trading setups and complex institutional arrangements.
- Organization: The top-level container for all your Prime accounts, typically representing your company or institution.
- Entity: A business unit within your organization, often used for different legal structures, geographical locations, or business divisions
- Portfolio: Individual trading accounts and vault wallets within an entity, used to segregate different strategies, teams, or purposes. User permissions are defined at this level.
Every Prime account begins with one portfolio under a single entity. You can add multiple portfolios within the same entity to separate trading strategies, user groups, or operational needs. Additional entities can be created for different domiciles or separate legal structures, with all entities from the same onboarding process rolling up into one organization.
API Key Hierarchy
API keys operate at three different scopes, each providing different levels of access:
Portfolio-level keys: Access only the specific portfolio they're created for. Required for Orders WebSocket and FIX connections. Created in the Prime UI.
Entity-level keys: Can perform REST API requests and subscribe to order book data via WebSocket on any portfolio within their entity. Created in the Prime UI.
Organization-level keys: Can perform REST API requests and subscribe to order book data via WebSocket across all portfolios across all entities within the organization. Can only be generated by emailing [email protected].
API keys also support IP allowlisting for enhanced security, allowing you to restrict access to specific IP addresses or CIDR ranges.
API Key Scopes
Through API scopes, Prime supports advanced operations for permissions setting, specifically by category or endpoint. For each API endpoint category (e.g. wallets, products, activities, etc), Prime supports setting API key scopes at a variety of complexities:
- Endpoint specific: Granular control where specific endpoints are allowed (e.g., get wallet balance is allowed but get portfolio balances isn't)
- Category-level READ/WRITE: All endpoints of a specific operation type within a category (e.g., all READ orders endpoints but no WRITE orders endpoints)
- ALL READ / ALL WRITE: Broad access that includes all categories for the specified operation type
This system is designed to work for both existing and future endpoints, so there is no need for further scoping in scenarios 2 and 3 as new endpoints are added.
Since most REST API calls require an Entity ID or Portfolio ID, your first API call should be List Portfolios to retrieve these identifiers and understand your account structure.
```java wrap theme={null} PortfoliosService portfoliosService = PrimeServiceFactory.createPortfoliosService(client);ListPortfoliosResponse response = portfoliosService.listPortfolios();
```
To learn more about this SDK, please visit the [Prime Java SDK](https://github.com/coinbase/prime-sdk-java).
```csharp wrap theme={null}
var portfoliosService = new PortfoliosService(client);
var response = portfoliosService.ListPortfolios();
```
To learn more about this SDK, please visit the [Prime .NET SDK](https://github.com/coinbase/prime-sdk-dotnet).
```go wrap theme={null}
portfoliosService := portfolios.NewPortfoliosService(client)
request := &portfolios.ListPortfolios{}
response, err := portfoliosService.ListPortfolios(context.Background(), request)
```
To learn more about this SDK, please visit the [Prime Go SDK](https://github.com/coinbase/prime-sdk-go).
```python wrap theme={null}
from prime_sdk.credentials import Credentials
from prime_sdk.client import Client
from prime_sdk.services.portfolios import PortfoliosService, ListPortfoliosRequest
credentials = Credentials.from_env("PRIME_CREDENTIALS")
client = Client(credentials)
portfolios_service = PortfoliosService(client)
request = ListPortfoliosRequest()
response = portfolios_service.list_portfolios(request)
```
To learn more about this SDK, please visit the [Prime Python SDK](https://github.com/coinbase/prime-sdk-py).
```bash wrap theme={null}
primectl list-portfolios --entity-id ENTITY_ID_HERE
```
```js wrap theme={null}
const portfoliosService = new PortfoliosService(client);
portfoliosService.listPortfolios().then(async (response) => {
console.log('Portfolios: ', response);
})
```
To learn more about this SDK, please visit the [Prime TS SDK](https://github.com/coinbase/prime-sdk-ts).
Most endpoints are scoped to the portfolio level, so they require a Portfolio ID. These include placing an order or creating a withdrawal. Examples of endpoints that are scoped to the entity level include listing payment methods, listing assets, and listing users.
Supported Assets
An asset can be any cryptocurrency (e.g., BTC) or fiat currency (e.g., USD) supported by Coinbase Prime. This is different from a product, which is a tradable pair of assets (e.g., BTC-USD). To retrieve a list of supported assets along with important metadata (precision, supported networks, etc.), call List Assets. This endpoint covers all assets at the entity level, so an Entity ID is required.
```java wrap theme={null} AssetsService assetsService = PrimeServiceFactory.createAssetsService(client);ListAssetsRequest request = new ListAssetsRequest.Builder()
.entityId("ENTITY_ID_HERE")
.build();
ListAssetsResponse response = assetsService.listAssets(request);
```
To learn more about this SDK, please visit the [Prime Java SDK](https://github.com/coinbase/prime-sdk-java).
```csharp wrap theme={null}
var assetsService = new AssetsService(client);
var request = new ListAssetsRequest("ENTITY_ID_HERE");
var response = assetsService.ListAssets(request);
```
To learn more about this SDK, please visit the [Prime .NET SDK](https://github.com/coinbase/prime-sdk-dotnet).
```go wrap theme={null}
assetsService := assets.NewAssetsService(client)
request := &assets.ListAssetsRequest{
EntityId: "ENTITY_ID_HERE",
}
response, err := assetsService.ListAssets(context.Background(), request)
```
To learn more about this SDK, please visit the [Prime Go SDK](https://github.com/coinbase/prime-sdk-go).
```python wrap theme={null}
from prime_sdk.credentials import Credentials
from prime_sdk.client import Client
from prime_sdk.services.assets import AssetsService, ListAssetsRequest
credentials = Credentials.from_env("PRIME_CREDENTIALS")
client = Client(credentials)
assets_service = AssetsService(client)
request = ListAssetsRequest(
entity_id="ENTITY_ID_HERE"
)
response = assets_service.list_assets(request)
```
To learn more about this SDK, please visit the [Prime Python SDK](https://github.com/coinbase/prime-sdk-py).
```js wrap theme={null}
const assetsService = new AssetsService(client);
assetsService.listAssets({
entityId: 'ENTITY_ID_HERE'
}).then(async (response) => {
console.log('Assets: ', response);
})
```
To learn more about this SDK, please visit the [Prime TS SDK](https://github.com/coinbase/prime-sdk-ts).
```bash wrap theme={null}
primectl list-assets
```
To learn more about this CLI, please visit the [Prime CLI](https://github.com/coinbase-samples/prime-cli).
Please note: All requests discussed above require proper authentication. For more information, visit REST API Authentication.
- Vorherrschende Sprache
- Java
- Sterne
- 3
- Forks
- 4
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
apache/rocketmq-dashboard#6872 ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ADORSYS-GIS/token-status-link#168 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ADORSYS-GIS/keycloak-oid4vp-plugin#232 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Type/Improvement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
wso2/product-integrator-mi#5099 ·
Maintainer antworten meist innerhalb von 1 Tag