DiscogsApiClient 2.1.1
See the version list below for details.
dotnet add package DiscogsApiClient --version 2.1.1
NuGet\Install-Package DiscogsApiClient -Version 2.1.1
<PackageReference Include="DiscogsApiClient" Version="2.1.1" />
paket add DiscogsApiClient --version 2.1.1
#r "nuget: DiscogsApiClient, 2.1.1"
// Install DiscogsApiClient as a Cake Addin #addin nuget:?package=DiscogsApiClient&version=2.1.1 // Install DiscogsApiClient as a Cake Tool #tool nuget:?package=DiscogsApiClient&version=2.1.1
DiscogsApiClient
This is a C# .Net6 library for accessing the Discogs API v2.0.
It allows for accessing and modifying a user's collection and wantlist and querying the Discogs database. For authentication can be chosen between personal access tokens or OAuth 1.0a.
This is a private project and not all Api functions are implemented. I might however add more functionality by request if my time allows for it.
Authentication
The DiscogsApiClient supports authentication by either using a user's personal access token or the full OAuth 1.0a auth flow.
Personal access tokens are the easiest way to make authenticated requests since it only requires the user to generate an access token in the development section of their profile settings. This might not be a great user experience for an application but is useful if the DicogsApiClient is used behind an Api as part of a service or in any other head-less scenario.
The OAuth Flow on the other hand allows the user to log in with their Discogs credentials directly in the application and authorize it to make requests on the user's behalf. This requires the application to be registered by the developer in their development profile section and obtain its Consumer Key and Consumer Secret with which the application can fetch a Request Token from the Discogs Api. With this token the application needs to open Discog's login page and specify a local Url to which the page will redirect after successful login to pass back a Verifier Key with which the final OAuth Token and OAuth Token Secret, needed for the client to be authenticated, are requested. The final token and secret are permanently valid and should be stored so that the user only needs to log in once.
Note: The OAuth flow is implemented in the plain version without encrypting/hashing the tokens because the Discogs Api is only accessible over Https which ensures a secure connection. Doing it this way is even recommended by the Discogs documentation.
Getting Started
Download the Nuget Package or compile the library from source.
The easiest way to use the library now is using it with Dependency Injection with either a user token
// At startup register the DiscogsApiClient and the authentication provider.
services.AddDiscogsApiClient("YourAwesomeApp/1.0.0");
services.AddDiscogsUserTokenAuthentication();
// Inject the IDiscogsApiClient and authenticate with the user token.
var authRequest = new UserTokenAuthenticationRequest("PersonalAccessTokenFromDiscogs");
var authResponse = await discogsApiClient.AuthenticateAsync(authRequest, default);
// Use the authenticated client.
var response = await discogsApiClient.GetIdentityAsync(default);
or the OAuth flow:
// At startup register the DiscogsApiClient and the authentication provider.
services.AddDiscogsApiClient("YourAwesomeApp/1.0.0");
services.AddDiscogsPlainOAuthAuthentication();
// Inject the IDiscogsApiClient and authenticate with the OAuth flow.
var authRequest = new PlainOAuthAuthenticationRequest("YourAwesomeApp/1.0.0",
"ConsumerKeyFromDiscogs", "ConsumerSecretFromDiscogs",
"http://localhost/verifier", GetVerifierKey)
{
AccessToken = "StoredAccessTokenIfPreviouslyAuthenticated",
AccessTokenSecret = "StoredAccessTokenSecretIfPreviouslyAuthenticated"
};
var authResponse = await discogsApiClient.AuthenticateAsync(authRequest, default);
// Use the authenticated client.
var response = await discogsApiClient.GetIdentityAsync(default);
// Demo method which handles the user login & returns the verifier token
public Task<string> GetVerifierKey(string authUrl, string callbackUrl, CancellationToken token)
{
// Open browser with authUrl
// Detect redirect to callbackUrl
// Verifier Token will be appended to the url with a '?': http://localhost/verifier?verifierkey
// Parse token from url and return it
}
The client can still be constructed and used without Dependency Injection. Instantiation and handling of the Httpclient then needs to happen manually.
Following is example code for using the DiscogsApiClient without using Dependency Injection.
With user token:
var userAgent = "YourAwesomeApp/1.0.0";
var userToken = "PersonalAccessTokenFromDiscogs";
var httpClient = new HttpClient();
httpClient.DefaultRequestHeaders.UserAgent.ParseAdd(userAgent);
var authProvider = new UserTokenAuthenticationProvider();
var apiClient = new DiscogsApiClient(httpClient, authProvider);
var authRequest = new UserTokenAuthenticationRequest(userToken);
var authResponse = await apiClient.AuthenticateAsync(authRequest, CancellationToken.None);
if (authResponse.Success)
{
// Test call retrieves the identity of the authenticated user
var identity = await apiClient.GetIdentityAsync(CancellationToken.None);
}
else
{
log.Error(authResponse.Error);
}
With OAuth flow:
var userAgent = "YourAwesomeApp/1.0.0";
var callbackUrl = "http://localhost/verifier";
var consumerKey = "ConsumerKeyFromDiscogs";
var consumerSecret = "ConsumerSecretFromDiscogs";
var accessToken = "StoredAccessTokenIfPreviouslyAuthorized";
var accessTokenSecret = "StoredAccessTokenSecretIfPreviouslyAuthorized";
var httpClient = new HttpClient();
httpClient.DefaultRequestHeaders.UserAgent.ParseAdd(userAgent);
var authProvider = new PlainOAuthAuthenticationProvider();
var apiClient = new DiscogsApiClient.DiscogsApiClient(httpClient, authProvider);
var authRequest = new PlainOAuthAuthenticationRequest(userAgent, consumerKey, consumerSecret, callbackUrl, GetVerifierKey)
{
AccessToken = accessToken,
AccessTokenSecret = accessTokenSecret
};
var authResponse = await apiClient.AuthenticateAsync(authRequest, CancellationToken.None);
if (authResponse.Success)
{
var accessToken = authResponse.AccessToken;
var accessTokenSecret = authResponse.AccessSecret;
// Store token & secret
// Test call retrieves the identity of the authenticated user
var identity = await apiClient.GetIdentityAsync(CancellationToken.None);
}
else
{
log.Error(authResponse.Error);
}
public Task<string> GetVerifierKey(string authUrl, string callbackUrl, CancellationToken token)
{
// Open browser with authUrl
// Detect redirect to callbackUrl
// Verifier Token will be appended to the url with a '?': http://localhost/verifier?verifierkey
// Parse token from url and return it
}
After successfully setting the client up and being authenticated you can make e.g. a database query:
var queryParams = new SearchQueryParameters { Query = "hammerfall", Type = "artist" };
var paginationParams = new PaginationQueryParameters(1, 50);
var response = await apiClient.SearchDatabaseAsync(queryParams, paginationParams, CancellationToken.None);
Changelog
1.0.0
- Initial release.
- Support for User Token & OAuth 1.0a authentication flows.
- Implementation of Api functions for user information, collection & wantlist and database queries.
2.0.0
- Refactored the library for Dependency Injection support:
- Added IServiceCollection extension methods to support easy dependency injection.
- Added IDiscogsApiClient interface for mocking and Dependency Injection.
- The DiscogsApiClient's HttpClient is now injectable via the constructor.
- If configured via the IServiceCollection the HttpClient will be injected via the IHttpClientFactory.
- Needed parameters for the IAuthenticationProviders are moved from their constructors into their IAuthenticationRequest implementations.
- Sealed all classes for performance.
- Refactored the library for Dependency Injection support:
2.1.0
- Added missing pagination parameter to GetCollectionFolderReleasesByFolderIdAsync method.
2.1.1
- Fixed URL not being formatted correctly for GetCollectionFolderReleasesByFolderIdAsync method.
Roadmap
- More granular authentication requirements for requests (not all requests need it)
- Rate limiting support
- CI/CD
Implemented Api Functions
The current implementation of the Api surface is focused on querying the database and accessing the user's collection and wantlist.
For simplicity reasons the client needs to be authenticated for all Api requests.
User resources
- Get user information
- Collection
- Get all collection folders
- Get, Create, Update, Delete collection folders
- Get releases in a collection folder
- Add, Remove releases from a collection folder
- Wantlist
- Get releases on the wantlist
- Add, Delete releases to/from the wantlist
Database resources
- Discogs database search
- Get master release
- Get artist & artist's releases
- Get release & release's community rating
- Get label & label's releases
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- Microsoft.Extensions.Http (>= 6.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
4.0.0 | 263 | 12/13/2023 |
4.0.0-beta.3 | 122 | 10/30/2023 |
4.0.0-beta.2 | 82 | 10/30/2023 |
4.0.0-beta.1 | 106 | 8/23/2023 |
3.1.0 | 235 | 7/3/2023 |
3.0.1 | 256 | 4/1/2023 |
3.0.0 | 258 | 3/19/2023 |
2.1.1 | 364 | 11/7/2022 |
2.1.0 | 420 | 10/22/2022 |
2.0.0 | 447 | 9/25/2022 |
1.0.0 | 435 | 9/6/2022 |
Fixed URL not being formatted correctly