Deezer API endpoint with details about parnter/co-branded subscription - deezer

I'm looking for Deezer API endpoint returning info about subscription via partner and/or co-branding detail.
For example, similar data as available on https://www.deezer.com when signed in with an account subscribed with a partner/co-branding options (available in included javascript):
var CUSTO = {
"id":0,
"logos": {
"header":"logo_telekomslovenije_trans-v00341265",
"logo_link":"",
"logo_position":"bottom"
},
"tab_header":{
"name":"",
"color":"",
"url":"",
"iframe_url":"",
"iframe_height":760,
"iframe_width":"990px"
},
"store_platform":"deezer"
};
var COBRANDING = 'none';
Additionally it might be handy if available subscription INFOS / offers http://api.deezer.com/infos would also contain partner/co-branded subscription options for given country of unsubscribed (free) user.
Thank you.

Unfortunately, these endpoints do not exist and will not be implemented, sorry.

Related

Using the ScanR API from gouv.fr for a POST request that, given a company name, returns its id

I'm trying to use the ScanR API:
Technical documentation: https://scanr-api.enseignementsup-recherche.gouv.fr/api/swagger-ui.html
General presentation: https://api.gouv.fr/les-api/scanR
Online interface: https://scanr.enseignementsup-recherche.gouv.fr/
My goal is to give the API a structure/company name, and receive, among others, a structure/company id. Then I am able use the GET endpoint '/v2/structures/structure/{id}' to access the description.
I believe that to do this, I would use the POST endpoint '/v2/structures/search'.
However, I don't manage to structure the query in a way that works.
Can anyone give me an example?
The scanR team kindly provided an example that I share here:
url_structures = "https://scanr-api.enseignementsup-recherche.gouv.fr/api/v2/structures/search"
my_query = "carbon\ waters"
params = {
"pageSize": 12,
"query": my_query
}
scanr_output = requests.post(url_structures, json=params).json()

Getting response from API - DialogFlow Chatbot

I am creating a chatbot using DialogFlow. Here, I am trying to get response from the API, which has been created by my development team (using python). They provided the API URL and requested to fetch data from it according to the users query. I have created a function in the inline editor and pasted the given API URL.
Below is the API format they have created,
{
“data”: [{
“pincode”: “”,
“location_formatted_address”: “”,
“user_id”: “”,
“department_name”: “Education”,
“locality”: “”,
“status”: “Select_Status”
}]
}
Here, when a user gives a department name, it must respond the user with locality of that specific department.
In the Inline editor, I have applied the following logic to fetch the locality,
function getDatafromApI(agent){
const name = agent.parameters.name;
return getAPIData().then(res => {
res.data.map(issues => {
if(issues.department_name === name)
agent.add(`${name}. ${issues.locality}`);
intentMap.set('Fetch API', APIData);
In the above code, "name" is the parameter given in the intent section.
But, I am not getting any response. Any help?
The inline editor uses Firebase. You will have to upgrade to Firebase "Blaze" OR "Flame" plan as the "Spark"(free) plan does not allow external api calls.
However if you have already upgraded Firebase plan and still seeing this error, you can see the execution logs by clicking "view execution logs" link at bottom of Dialogflow fulfillment window.

Get the num followers with linkedin API v2

The num followers of linkedin API is not working anymore. We used to use https://api.linkedin.com/v1/companies/11543/num-followers, but it responds with the error listed below.
{
"errorCode": 0,
"message": "This resource is no longer available under v1 APIs",
"requestId": "EUBVUH7QTU",
"status": 410,
"timestamp": 1561391381048
}
We need to get this number with v2 but it seems to have been deprecated in v2 according to these docs.
The totalFollowerCounts field is deprecated and will stop being
included in responses after January 31, 2019.
Is there a way to get the number of followers using V2 of LinkedIn's API?
David.
I think you already know that V1 Api version has been deprecated, and you have to migrate all your code to the new V2 endpoints.
Assuming your APP already has access to the V2 version, you can get the follower statistics using this V2 endpoint.
If you need to get the followers statistics by segments, you can use this other endpoint, where you can pass many arguments (region, language, seniority...)
You can access the followers using the following url
https://www.linkedin.com/pages-extensions/FollowCompany?id={companyId}&counter=bottom
Replace companyId with your companyId.
This will result in a webpage that can be easily parsed.
result
Example in code:
var client = new HttpClient();
var request = new HttpRequestMessage(HttpMethod.Get, "https://www.linkedin.com/pages-extensions/FollowCompany?id={companyId}&counter=bottom");
var response = await client.SendAsync(request);
response.EnsureSuccessStatusCode();
var payload = await response.Content.ReadAsStringAsync();
var doc = new HtmlDocument();
doc.LoadHtml(payload);
var node = doc.DocumentNode.SelectNodes("//div[contains(#class, 'follower-count')]");
var f = node.FirstOrDefault().InnerText;
source: https://taras.codes/blog/linkedin-organization-follower-count/
It seems that your app doesn't have full access to the V2 version of the Linkedin API, because I assume your token can manage the company with ID 11543, right?
In this case, you have to apply to the Marketing Developer Platform, accesible from the Linkedin Apps Console, because the access to V2 version is restricted, and not all apps that apply get this permission.

Add a subpanel record to a SugarCRM account through REST API

Question: How do I create a subpanel record through the SugarCRM rest api endpoint for accounts?
Steps taken so far:
I've added a new package called, "transactionHistory" with a module named, "InvoiceHistory" using the SugarCRM studio.
I added a One to Many relationship to the Accounts module using studio.
I'm using NetSuite to push new invoices to the new module's record via the subpanel "create" option. Here's the code I'm using:
function createSugarTransaction(transaction, token) {
var url = 'https://crm.techsoft3d.com/rest/v10/Accounts/' + transaction.customer;
var headers = {
"Content-Type": "application/json",
"OAuth-Token": token
};
var now = (new Date()).toISOString();
var body = {transactionHistory_InvoiceHistory:
{
create: [{
name: transaction.docId,
transaction_date_c: transaction.date,
invoice_status_c: transaction.status,
due_date_c: transaction.duedate,
total_amount_c: transaction.total,
amount_due_c: transaction.remaining,
start_date_c: transaction.startdate,
end_date_c: transaction.enddate
}]
}
};
var response = nlapiRequestURL(url, JSON.stringify(body), headers, 'PUT');
return response;
}
The transaction object has been validated and the json object within the create: [] array has matching sugar fields (key) with the corresponding transaction object values.
When making the API call to sugar I'm successfully authenticated and have access to the custom module and accounts - so no problem there. However, when the call is returned to response it's showing the following error:
{"error":"no_method","error_message":"Could not find a route with 1 elements"}
I'm unsure of what else is needed in order for the record to be created. According to sugar's help documentation and developer community this should work. I'm using the basic information provided by sugarcrm support portal:
http://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.6/API/Web_Services/Examples/v10/module_POST/
According to other blog posts within the developer community, it should be as simple as adding the subpanel name, followed by an array of fields under the "create" object... similar to this:
var requestBody = { package_module:create[{name:value}]};
My initial thinking of what's wrong is:
1. my package_module name isn't correct, but I'm unable to find it anywhere within the applicaiton or help documentation.
2. the request body isn't formatted properly, even though it's structure was copied from this article https://developer.sugarcrm.com/2014/02/28/sugarcrm-cookbook2/
Any help would be appreciated.
try the createRelatedRecord api endpoint
type {sugarurl}/rest/v10/help to see a list of endpoints to look through, most of which have documentation and examples
https://crm.techsoft3d.com/rest/v10/help
your API url should have the name of the link (relationship) you want, in addition to the values in the POST payload
https://crm.techsoft3d.com/rest/v10/Accounts/{transaction.customer}/link/accounts_transactionhistory (or whatever your link's name is)
per the documentation for this endpoint, you just specify the field values in the payload
{
"first_name":"Bill",
"last_name":"Edwards"
}

GetPrePaymentDisclosure returning Internal Error

I'd like to use this endpoint to display the calculated fees on my site before taking the user to the paypal site; however, when I query the endpoint with a valid payKey, I receive an internal error.
Endpoint: https://developer.paypal.com/docs/classic/api/adaptive-payments/GetPrePaymentDisclosure_API_Operation/
To generate the payKey, I'm POSTing to svcs.sandbox.paypal.com/AdapativePayments/Pay with the following request body:
{
"actionType":"PAY",
"currencyCode":"USD",
"feesPayer":"SENDER",
"requestEnvelope": { "errorLanguage": "en_US" },
"cancelUrl":"test.com/cancel",
"returnUrl":"test.com/return",
"receiverList": {
"receiver": [
{ "email": "someguy#email.com", "amount": "80.00" }
]
}
}
Any ideas as to what's going on?
Note: I had to edit out the valid URLs because I don't have enough reputation.
For GetPrePaymentDisclosure you must supply senderEmail in the PAY request for it to function.
This is because GetPrePaymentDisclosure is supposed to be used to determine the status of the transaction and see if it is covered by the Remittance Transfer Rule.
From the Documentation: This API is specific for merchants who must support the Consumer Financial Protection Bureau's Remittance Transfer Rule.
It does not work to determine the fees beforehand if it does not hit these rules. As all you will get back is [status] => NON_RTR with no information.
If you would like this functionality outside of RTR transactions you should submit a feature request on PayPal's Technical Support Site