docusignapi - DocuSign: Getting envelope info -


i've uploaded test file docusign document id response: 08eebff6-0cbc-4831-b317-c73ba3e2f61d

when try read with:

https://demo.docusign.net/restapi/v2/accounts/<account_id>/envelopes?from_date=2010-01-01

i empty envelope response:

{     "resultsetsize": "0",     "totalsetsize": "0",     "nexturi": "",     "previousuri": "",     "envelopes": [] }

when try read with: https://demo.docusign.net/restapi/v2/accounts/<account_id>/envelopes/08eebff6-0cbc-4831-b317-c73ba3e2f61d/documents

i proper response:

{     "envelopeid": "08eebff6-0cbc-4831-b317-c73ba3e2f61d" }

for understanding, expect result in first response such envelope id in example above should in envelopes array in first response. correct or doing wrong here?

in first step, assume meant created envelope not document. yes?

did send envelope or create it? (a draft)

if sent envelope properly, agree should have shown in envelopes: liststatuschanges query. see if envelope shows in web browser @ demo.docusign.net

you can try liststatuschanges method via api explorer.

you can improve question showing response initial envelopes: create call.

update: created draft envelope , did not show in liststatuschanges results. newly created sent envelope listed. i'm not sure if design or not, enquire docusign engineering group.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more