I'm using Docusign's REST API for creating template and sending it to the customer to sign it - everything works fine but the template doesn't display the labels of the tabs (textTabs), there are their names showed only
I'm sending everything in an evelope, an item looks like this:
"textTabs": [
{
"anchorString": "app_contractbundle_contract_masterAgreement_salesforceId",
"anchorUnits": "pixels",
"anchorXOffset": 105,
"anchorYOffset": -3,
"documentId": 1,
"name": "masterAgreement_salesforceId", - this is displayed in the template
"pageNumber": null,
"xPosition": 0,
"yPosition": 0,
"tabLabel": "Salesforce ID", - this should be displayed
"value": null,
"fontSize": null,
"locked": true,
"required": true
},
Thanks!
It's not documented well in the API docs but the name property is what's used for the help tip on tabs, not the tabLabel. Either switch your values or just set the name to the same thing as your tabLabel.
Related
We have implemented the createDraftListing API using this documentation to create new listing on etsy.
But we are not able to post below field using above API because in documentation request parameter this field are not present.
Also we have added the item weight, item length, item width and item height in request feed and posting this value to above api call but still showing blank on products.
Request feed:
{
"title": "this is my title",
"description": "this is my description",
"quantity": "100",
"state": "active",
"price": 44.55,
"who_made": "collective",
"when_made": "2020_2022",
"listing_type": "physical",
"shipping_profile_id": 12345678,
"processing_min": 1,
"processing_max": 1,
"item_weight": "0.71",
"item_weight_unit": "lb",
"item_length": 5.5,
"item_width": "7.5",
"item_height": 0.75,
"item_dimensions_unit": "in",
"has_variations": false,
"language": "en-US",
"is_taxable": true,
"should_auto_renew": true,
"is_customizable": true,
"is_personalizable": true,
"personalization_is_required": true,
"personalization_char_count_max": 1,
"personalization_instructions": "",
"taxonomy_id": 2279
}
So please let us know any api to post above fields to etsy?
Thanks.
first you can get id shipping profile id in get shipping profile api. I try and success
We have implemented the createDraftListing API using this documentation to create new listing on etsy.
But we are not able to post below field using above API because in documentation request parameter this field are not present.
Also we have added the item weight, item length, item width and item height in request feed and posting this
value to above api call but still showing blank on products.
Product link
Request feed:
{
"title": "ArttoFrames Rustic Custom Picture Poster Frame 1 Wide 1343",
"description": "In a beautiful turqoise, this barnwood frame is the perfect accent to transform a room into a unique decorative space. Hang a few to create an edgy gallery wall or give it to a loved one as a housewarming or baby shower gift. Perfect in a children's room or in an airy living space.",
"quantity": "100",
"state": "active",
"price": 44.55,
"who_made": "collective",
"when_made": "2020_2022",
"listing_type": "physical",
"shipping_profile_id": 165973438594,
"processing_min": 1,
"processing_max": 1,
"item_weight": "0.71",
"item_weight_unit": "lb",
"item_length": 5.5,
"item_width": "7.5",
"item_height": 0.75,
"item_dimensions_unit": "in",
"has_variations": false,
"language": "en-US",
"is_taxable": true,
"should_auto_renew": true,
"is_customizable": true,
"is_personalizable": true,
"personalization_is_required": true,
"personalization_char_count_max": 1,
"personalization_instructions": "",
"taxonomy_id": 2279
}
How to post above fields to etsy?
I create Woocommerce products in my ionic app. I would like also to push the stock quantity when I create the product. However, the stock always is with NULL stored in my MYSQL DB. Here is the JSON feed
{
"product": {
"title": "test stock",
"stock_quantity": "35",
"images": [],
"post_author": 88,
"type": "simple",
"categories": []
}
}:
And here the piece of code from the app
var productInfo = {
title: this.productName,
regular_price: this.productPrice,
sale_price: this.productDiscount,
stock_quantity: this.productStock,
description: this.productDesc,
images: new Array<any>(),
post_author: this.userService.id,
type: this.productType,
categories: new Array<any>()
};
I tried different tags for stock_quantity like only "stock" and tried to push the variable with "" and without it. But I'm facing still the same issue.
Your JSON syntax is correct. Also, you are passing the correct parameter for the stock as stock_quantity and as I reviewed your JSON request you have not passed the manage_stock parameter as true by default that considers as false. so, you need to pass that parameter also.
You can try the following code.
{
"product": {
"title": "test stock",
"stock_quantity": "35",
"manage_stock": true,
"images": [],
"post_author": 88,
"type": "simple",
"categories": []
}
}:
you can refere the WooCommerce REST API Product Properties for create products
I want to search posts by categories in the WP-API.
I know I can search posts by the attribute categories or filter[cat].
But the posts contains more than one category.
I tried to search like this:
{host}/wp-json/wp/v2/posts?categories=69&filter[cat]=[228,246,237]&per_page=50
or
{host}/wp-json/wp/v2/posts?categories=69&filter[cat]=228&filter[cat]=246&filter[cat]=237&per_page=50
or
{host}/wp-json/wp/v2/posts?categories=69&categories=246&categories=237&categories=228
This didn't work for me. It caused the search to look for the last attribute.
Any ideas?
This is the structure of Json response
{
"id": 9333,
"date": "2016-08-02T14:17:01",
"date_gmt": "2016-08-02T12:17:01",
"guid": {
"rendered": "{post}/?p=9333"
},
"modified": "2016-08-03T08:50:35",
"modified_gmt": "2016-08-03T06:50:35",
"slug": "{post}",
"type": "post",
"link": "{host}/{post}/",
"title": {
"rendered": "{post}"
},
"content": {
"rendered": "{post}"
},
"excerpt": {
"rendered": "{post}"
},
"author": 3,
"featured_media": 0,
"comment_status": "closed",
"ping_status": "closed",
"sticky": false,
"format": "standard",
"categories": [
228,
237,
207,
217,
246,
231,
69,
221,
270,
244
],
"tags": [],
"_links": []
}
Thanks!
If you want to get posts from multiple categories, there are few solutions, depending from your needs.
In case when you want to get posts from category with ID = 1 OR category with ID = 2 use the following URL:
http://localhost/lifelog/wp-json/wp/v2/posts?filter[cat]=1,2
or:
http://localhost/lifelog/wp-json/wp/v2/posts?categories=1,2
For case when you want to get posts from category with ID = 1 AND category with ID = 2 you can use:
http://localhost/lifelog/wp-json/wp/v2/posts?filter[category__and][]=1&filter[category__and][]=2
BUT - some filter values used in the filter array needs authenticated user with edit_posts privileges.
Fortunately, there is a more simple solution - WordPress supports links like:
http://example.com/category/test1+test2/
Under above URL you will get list of posts which are assigned to the test1 AND test2 categories. And in the REST API you can achieve the same behaviour with the following URL:
http://localhost/lifelog/wp-json/wp/v2/posts?filter[category_name]=test1%2Btest2
Please remember that you have to replace the + sign into %2B.
I've been using the Graph API for contact creation and synchronization between a master account and all of our organization's Office 365 accounts. This has been working well up until the past month or so.
My synchronization process involves querying a specific folder of the master account for contacts, caching them, and then running through the list of target users, creating contacts where necessary. Getting lists of contacts, creating contact folders, and deleting contacts all still works as expected. Creating a contact returns "ErrorInternalServerError: Object reference not set to an instance of an object."
I have been using the client_credentials flow and checked that my app has the appropriate credentials in the Azure AD admin panel. Below is the JSON object that I'm POSTing for contact creation. This is happening regardless of contact, or target user.
{
"categories": [],
"birthday": null,
"fileAs": "GPS 00 Bob, Todd",
"displayName": "GPS 00 Bob, Todd",
"givenName": "Todd",
"initials": "T.G.0.B.",
"middleName": "",
"nickName": null,
"surname": "GPS 00 Bob",
"title": "",
"yomiGivenName": null,
"yomiSurname": null,
"yomiCompanyName": null,
"generation": "",
"emailAddresses": [
{
"name": "Email",
"address": "todd.bob#contactsyncing.com"
}
],
"imAddresses": [
""
],
"jobTitle": "Chief Financial Officer",
"companyName": "",
"department": "",
"officeLocation": null,
"profession": null,
"businessHomePage": null,
"assistantName": null,
"manager": null,
"homePhones": [
""
],
"mobilePhone": "",
"businessPhones": [
""
],
"homeAddress": {
"street": "",
"city": "",
"state": "",
"countryOrRegion": "",
"postalCode": ""
},
"businessAddress": {
"street": "701 East Lumbar Ave",
"city": "Minot",
"state": "ND",
"countryOrRegion": "United States of America",
"postalCode": "68745"
},
"otherAddress": {},
"spouseName": null,
"personalNotes": null,
"children": []
}
edit
Additional information: I am posting to a specific contact folder with its ID. Here is an example of the URL: https://graph.microsoft.com/v1.0/users/91bbdb7b-3b41-474c-93c9-99b1da960c18/contactFolders/AAMkADFlNzQ5NGQ5LTEwNjYtNGFiZS04NDlhLTViOGE0YzMzZjI3OQAuAAAAAAA9YtgrncHYSKObisZl7JkCAQChpNwDV4FXRaJC6UF1HyyuAAAAAAFFAAA=/contacts
Is that contactFolder ID properly formed?
/edit
The script is written in PHP and I'm simply cURLing these requests. Any thoughts are suggestions would be greatly appreciated. Let me know if any other information would be helpful.
Thanks!
After filtering down contact fields to a bare minimum and then re-adding them one by one, I've found that the birthday field was at fault. It seems that the Graph API no longer accepts a null value for this. Removing the field completely if a birthday is not specified seems to have resolved the issue.
I consider this resolved. Perhaps the Graph API documentation should be updated to reflect this fact? Additionally, it would seem prudent to improve the API's response to this error. "InternalServerError" does not adequately describe the cause.
Thanks!