Skip to content

Commit

Permalink
Merge pull request #60 from holaplex/sep-7-release
Browse files Browse the repository at this point in the history
Sep 7 release
  • Loading branch information
mackenziewildman authored Sep 11, 2023
2 parents d9d3fd5 + 828ab19 commit d9c53b9
Show file tree
Hide file tree
Showing 2 changed files with 53 additions and 0 deletions.
46 changes: 46 additions & 0 deletions docs/hub/Guides/switch-collection.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
sidebar_position: 10
---

# Move an NFT from one collection to another

The Hub API can be used to move an NFT from one collection to another. In order to use the `switchCollection` mutation, the following must be true:
- The NFT to be moved was created in Hub (or imported into Hub and has the Hub project treasury as its update authority)
- The NFT is on Solana
- The NFT is *not* compressed
- The destination collection belongs to the same Hub project as the original collection
- The destination collection was created in Hub (or imported into Hub and has the Hub project treasury as its update authority)

Upon switching collections, credits will be deducted from your organization's account. To view the number of credits charged for this or any action, view your organization's credit page: [https://hub.holaplex.com/credits/costs](https://hub.holaplex.com/credits/costs)

## Example

```graphql
mutation SwitchCollection($input: SwitchCollectionInput!) {
switchCollection(input: $input) {
collectionMint {
id
address
owner
}
}
}
```
Variables:
```json
{
"input": {
"mint": "<MINT-ID>",
"collectionAddress": "<COLLECTION-ADDRESS>"
}
}
```
Replace `<MINT-ID>` with the id of the mint to be moved and `<COLLECTION-ADDRESS>` with the on-chain address of the destination collection.

As with all Hub API calls, you'll need an access token that can be generated on your organization's Credentials tab: [https://hub.holaplex.com/credentials](https://hub.holaplex.com/credentials)
For all API requests to Hub, you'll need to include an authentication header of the form. This token should be included in the call's header:
```json
{
"Authorization": "<access-token>"
}
```
7 changes: 7 additions & 0 deletions docs/hub/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,13 @@ sidebar_position: 7

# Release Notes

## September 7, 2023

Features:

- Switch collection through HUB API - move a HUB-generated NFT from one HUB collection to another
- Retry with exponential backoff on all Solana RPC calls - this prevents the user from needing to trigger a retry in the case of an RPC failure

## August 17, 2023

Features:
Expand Down

0 comments on commit d9c53b9

Please sign in to comment.